| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| This is one time you can do it easier without using embed code. Define the filter string as a CSTRING and pass it to the process as a parameter. define a local CSTRING variable called FilterString Assign the passed string to the local string inside ThisWindow.Init Now back in the process properties screen assign !FilterString as the filer. The exclamation mark says it's a variable that holds the string. Now you can pass any filter expression to the process. You just need to do some code work to build the filter string as a CSTRING. Lets say the filter is to limit to a single InvoiceDate Filterstring = 'INV:InvoiceDate = ' & LocalUserDateVariable Now you have used a literal value in the expression and you don't need to bind it. Now you can make a nice window with all the filter options you like and then concatenate all the parts to send to your process. You could send the same string to a report too. There are some other tricks to this such as string literal values need quotes. I use '<39>' to show where I am concatenating quotes. It's easy to screw this part up so try to make it easy to read. On 11 Aug 2008 14:29:42 -0400, Ron Ronhovde <hpronhovde-NoSpam-@gmail.com> wrote: >I am trying to force myself to learn how to use some of the important >controls in templates. Right now I'm struggling with the 'Filter' in >the Process Template. I need to create a dynamic filter string >depending on selections the user makes. > --------------------------------------- Paul Blais - Hayes, Virginia |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.