Flow Options opinions
-
Hello All, I have a particular problem that I am hoping someone can give me a better way of acheiving something. I have a web page with some predefined search options. I want to give the user a way to create an adHoc search that could have up to 5 elements for the criteria. So I thought of associating a numeric or alpha character to each element and then do check for a pattern on the postback. This option is becoming cumbersome and I know there has got to be a better way of doing this. Any suggestions would be greatly appreciated. For those who don't answer, have a great day. Fred
-
Hello All, I have a particular problem that I am hoping someone can give me a better way of acheiving something. I have a web page with some predefined search options. I want to give the user a way to create an adHoc search that could have up to 5 elements for the criteria. So I thought of associating a numeric or alpha character to each element and then do check for a pattern on the postback. This option is becoming cumbersome and I know there has got to be a better way of doing this. Any suggestions would be greatly appreciated. For those who don't answer, have a great day. Fred
Create 5 fields.
Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
Create 5 fields.
Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
I did create 5 fields but what if the user doesn't want to utilize all the fields. For example they might want to use "Create Date" and "User". Another user might want to search by "Status", "User" and "Create Date".
Then what is the problem. Pass the parameters to your stored procedure if they are provided, null if not, and then use the appropriate where clause to restrict the results. If you aren't using a database, LINQ will do the same thing in its where clause.
Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane
-
Then what is the problem. Pass the parameters to your stored procedure if they are provided, null if not, and then use the appropriate where clause to restrict the results. If you aren't using a database, LINQ will do the same thing in its where clause.
Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane