We have a runtime application that has been distributed to many users. We have a new user who is running our software, runtime in Access 2002 on Windows XP Pro. When the program opens the first time the relinker does a test to see if the back end is where it is supposed to be using the dir() function. In this case the recommended path is in a table and we test against that. If it isn't there a dialog is opened so the person using the software can locate it with the File dialog. We have been using this for years with no problem. Now this client gets a "error 52 bad file name or number" error message on the module that does the BE location checking. I looked in the module and the only place it could be generated is a line with the Dir() function. My assumption is something is hosed with the Access runtime installation. We have tested the installation disk in every way we can and can not get the error. I have done every thing I can think of to the Dir function and I can't recreate it.
Assuming a reinstall does not fix the problem any one have any more thoughts on places to look. I did a Google search on this and the only problems I can find with Dir() are when it is used with network drives. This isn't the case here, everything is on the C drive.
Start Free Trial
