...missing or broken reference to the file 'filedialog.dll' error

[Bhaughbb]

I've been building a report that has the option to export the report per employee into a seperate file and to add more functionality to it I found this sample database and used the directory select to allow the user to define where the reports export to.

It works beautifully on my computer but as this is a shared database across our network and some people connect from outside using VNC it needs to work for them as well. When I went to demonstrate the feature to the department head who would be using it most often the database broke upon opening with the following error message:
[QUOTE
Your Microsoft access database or project contains a missing or broken reference to the file 'filedialog.dll' version 10.0

*To ensure that your database or project works properly, you must fix this reference.
][/QUOTE]
At which point every active bit of script like auto date fields suddenly didn't work and the entire database is non-functional. I can't find any reference to the dll in question and don't see a cause for it and could use some help. Since the file is over 100k after deleteing everythign I could in a copy of the database I've linked it off-site. Take a look Here, any help would be greatly appreciated as I would prefer not to have to hard-code a path as not everyone who uses this database will be computer savy enough to be able to manually type a path into a field.

Thanks for any input and advice!

Access 2000 database running on A2k3.

 

[boblarson]

Your database has a reference set to a file that contains HELPSTR_FILEDIALOGLib, that is a Crystal Reports file and if your other computers don't have Crystal Reports installed, then you will have a problem since they won't have that file.

The path looks like (and I can't make out the whole path due to it's length):
C:\Program Files\Common Files\Crystal Decisions\2.5\bin\filedi...

But, if you don't need that reference, try going in and unchecking it and closing the database file. Then reopen. It worked for me, but then I don't know what functionality that may have been there that just got lost; but you will know and if there is no loss in functionality, maybe the reference got set by something you started to do and decided against, or you accidentally checked the box while trying to check something else. Who knows? But if you just go into the references and uncheck the box and close and reopen the program, that will solve your immediate problem.

 

[ghudson]

But, if you don't need that reference, try going in and unchecking it and closing the database file. Then reopen. It worked for me, but then I don't know what functionality that may have been there that just got lost; but you will know and if there is no loss in functionality, maybe the reference got set by something you started to do and decided against, or you accidentally checked the box while trying to check something else. Who knows? But if you just go into the references and uncheck the box and close and reopen the program, that will solve your immediate problem.

Ditto to what boblarson says

 

[Bhaughbb]

Thanks! that seems to be the key to solving this issue. The hazards of having the developer's box that was built for me that isn't configured the same as everyone elses' in the office.