Every time I try to execute VBA code on my XP Pro machine, I get the following error message. It also happens when I try to edit VBA modules.

  How do I fix this? Do I need to re-install any .dll's?


Rand

__________________
Rand

Internally, access keeps a reference to the files used for string VBA code. Some times this references get corrupted and access can not find the file, even if you can open the code. This happens a lot (almost every time) when an access object that contains code gets imported into a database. Always remove the code from the object before importing into an access database.
The only way to fix this is to create a new database and import all of your objects into it. Copy the code into separate text files and under the object properties in design view, select hasmodule and click no.

Make a good backup before you begin this process. Yes, this has happened to me many times. :(




Sal

This sounds like a bug/feature to me.

Does MS have a bugfix/patch to solve this?

I use and re-use VB modules in many databases. This makes it a real pain to re-use code. I might as well be using PC File!



Rand

Use code modules more. This can be imported with no problem. Access is a good program, but it tries to do too much, and sometimes overtasking will kill you.

I use am using access more for the reporting than the forms. I do not keep data in access whenever possible.

make sure to decompile your file as well. This will reduce the possibility of bugs in your code. Do a search on this forum for "decompile" I do not remember it from the top of my head, but you run it from the command line.

Good luck.



Sal