Your ERP system is running the reports through its own viewer, correct?
One of two things is happening:
1. Are you using an ODBC connection to the SQL database? If so, it's not set up on the client machine or the client user doesn't have access to the network location of the database.
2. When you run a report from within VB, the application has to set the connection string for all of the tables in the report. Since the application only knows about report.mdb, that's the only connection that it's setting.
Try checking for the first issue, as that is one that you can resolve. If the problem is the second issue, you probably won't be able to fix it as the vendor will have to update their code to handle it.
-Dell