>>IMO, the article was pretty bad. I wrote to Whil and the author about it.
>>
>>- The author continually discusses "OCX" and then clearly uses syntax for creating an automation server.
>>- The author discusses using parameters to the report. This is fine when you have a single report, but one of the powerful features of Crystal is using sub-reports. Parameters don't work there. I've spent hours on the phone with Seagate Software tech support trying to do this. They admitted that it doesn't work. Same with defining the data file location at runtime. It has to be where you specify it.
>>- Why is the author playing around with the VB installer? There is a help file that ships with CR that tells you all the files you need to distribute.
>
>What problems do you have with data file locations at runtime ? Even with subreports I managed to get them right. For the parametersthing I don't know for sure, but I think it's possible in the same way.
>
>Just open the subreport with osubreport=opensubreport(Subreportname) command and set the datasources in the same way as the main report (using the oSubReport object).

I couldn't define the datafile locations for the subreports at runtime. It just wouldn't work, no matter what I tried. Tech support couldn't get it to work either. I finally decided to always put the data files in the same location everytime and always use the same name.