Incorrect Session Parameters while connecting to protected Access DB

[svelu]

I have a report which is having a subreport, both connecting to a protected MS Access DB (native connection) but to different queries. We are trying to run the report using the Crytal Report OCX from a VB application. If we change the location manually and propagate the location to subreport also then it works. But this is not going to work out at client's place since we don't know where the location of the MDB is going to be. We even downloaded 'update8.exe' from CrystalDecisions but it gives an error 'Could not locate procedure PESetDictionaryLocation from CRPE32.DLL' Is there any other elegant workaround?

Any immediate help is greatly appreciated.

Thanks,
S. Velu.