Hi,
How can I define a report so that whether the database file is on C, D or an other drive, I will not get an error when attempting to run a report from my program. Previously, I was able to run reports whose database was in a different location than the location set in the initial design of a report, without out a hitch.
For example, if the location/path at design time was C:\Pan\test.mdb, but myself or another user ran the front-end program who's database is at a different path (eg. C:\Pan2\test.mdb), the report would still run. Recently, however, if the actual path is different from the initial path, an error results.
How can I correct this so that I get the results I got before? Persons using the front-end program will not be able to open these report files and reset the location of the database.
One more thing, I noticed this problem occurred mostly with a report containing a sub report.
Thanks
How can I define a report so that whether the database file is on C, D or an other drive, I will not get an error when attempting to run a report from my program. Previously, I was able to run reports whose database was in a different location than the location set in the initial design of a report, without out a hitch.
For example, if the location/path at design time was C:\Pan\test.mdb, but myself or another user ran the front-end program who's database is at a different path (eg. C:\Pan2\test.mdb), the report would still run. Recently, however, if the actual path is different from the initial path, an error results.
How can I correct this so that I get the results I got before? Persons using the front-end program will not be able to open these report files and reset the location of the database.
One more thing, I noticed this problem occurred mostly with a report containing a sub report.
Thanks