OCX Parameters??

[blinder]

Hi,
In my application we register a Crystal rpt for use by users, and we store it as a binary in the database, so that a user can call the rpt from any client. The app places it into the ocx control etc - this works very well, is fast and means users can't stuff around with the rpt on disk.

My issue is "my apps registration process". When we read the rpt in, we want to query the rpt to find out what parameters it requires for the report to run, so that we can create, at runtime, a parameter entry form that fulfills the needs of the report.

Why you ask? - The person creating the report might not be the person doing the registering, and to keep our app tidy, it should manage the passing of parameters to the report. Every example I see in this forum assumes that the app knows the name of the parameter - what if it doesn't??? I want my app to dynamically handle the specific attributes of the report.

Thanks in advance for your help...

Peter

 

[blinder]

Well well well - No replies so far.

Having done some more research I have worked out that the answer might be in programming directly via API calls - In the last day I have replicated the OCX functionality that I currently use and am now onto solving the original question - Which is : for the rpt that I am working with - tell me the parameters it requires answers for, before it will run???

I hope this gives you more clues to helping me...

p.s. I come from New Zealand - The land of innovation