DLL problem?

[Dae Jeon]

I developed a VB program that uses Access(97) database.

I funny error happens sometimes:

Some users running the program on their PCs get the error message: “Bad file name or number ‘52’”.

When I debugged the program this error was triggered when attempting to open the Access 97 database that the program uses.

Opening up the database in question on my PC manually through the GUI interface and then running the program on it sometimes fixes the problem.

My suspicion is that it probably has something to do with the Access db and the DLL that the program uses to access it.

Anybody have any wild guesses or ideas?

Thanks in advance.

dkj kaj hj sj

[Iouri]

Try to repair and compact the database

Iouri Boutchkine
[email protected]

[Dae Jeon]

As I said previously that's what I did and that sometimes takes care of the problem but not all the time.
The other problem is that this problem never occurred while I was packaging the executable and DLLs with the Deployment Wizard that comes with VB 6.0, but it started occurring after I transitioned to InstallShield to package the exe and DLLs.

Bottom line, it is not acceptable to my users to repair and compact each time this occurs (for one thing the db is password protected and not to be opened manually by the user).

Any other solutions?


dkj kaj hj sj