Running Runtime via .dll

[JeffBarefoot]

When launching the Runtime with .dll functions, do the .dll functions override the values that would normally be stored in the report control file? Or does it simply populate the appropriate field in the control table?____For example..... if I set a filter using the setFilter() function does it override the values that may be stored in ri_filter? Or can I set the filter using setFilter() and get rid of the ri_filter field altogether? ____The reason that I^m asking is because the R&R documentation states that a filter can be 1024 characters long. If I^m using a control table that is a Visual FoxPro table the filter will be limited to 254 characters, the maximum length of a VFP field (except for a memo field, which doesn^t seem to work in this situation).____Thanks!____Jeff__Jeff

[FRED_EMMERICH_(Guest)]

I use the runtime .dll and I have to pass in all my data with the function calls.

[Dave_Francis_(Guest)]

Yes, forget the control file - just use the DLL. The RIPARAM() function gives you the chance to interact with the report before printing. So, for instance, you can pump dates straight into the report, get the report to trigger processes within your app, etc all before you run it. This means that you can code slick data extraction/analysis functions in your app which you can call by simply creating a calculated field with an expression of ____RIPARAM("RUNXPROC")____You simply cycle through all the RiParam() fields and do what they tell you before letting the report run.____So simple changes to a report can call powerful function in the app - best of both Worlds again.____Dave Francis____

[Jeff_Barefoot_(Guest)]

Thanks!