A little help(2nd Req.): OCX usage

[rokosz]

I really need a response to this:____The R&R sample SQL rsw32.ocx app runs fine.____Attempting the same effort (using the same pathxxx.rsw) in an ASP does not. ____The ocx will respect & use the username and password parameters. This shows that it does respond, at run-time, to at least some minimal amount.____The rsreport1.reportname is set at design time as desired.____However, at run time, an Common Dialog _always_ appears titled "Open Report". This dialog does respect the rsreport1.WindowTitle in the start bar.____At design-time it behaves flawlessly and exactly as expected. At run-time it mis-steps.____It appears that the report viewer is not getting everything it should from the OCX properties. The common dialog does allow selection of the desired report (after drilling down) and runs it without issue.____Is this loss of parameter information a known bug? ____I sense this isn^t by design. Is the ocx not recommended for use outside of VB? ____If it is recommended for use outside VB - in which environments/platforms/languages?____thanks, Bryan____rokosz__

[kfleming]

VB is our primary test environment but any application that allows you to include an activeX control should work as long as you follow whatever rules that are imposed by that application.____Do you have VB so that you could try the same code there?______Kathleen__R&R Support

[rokosz]

yes, that^s what I assumed (re OCX running "anywhere" supporting OCX.____The code tested (which drops the .reportname parameter) in ASP -- runs fine in VB6 - The code tested doesn^t drop any other parameters - only the reportname.____Bryan