An early release of Access 2000 had a very nasty issue like that, but this
horrid bug was fixed. If your issue is related to this, you need to download
your updates for Office 2000:
http://support.microsoft.com/?id=304548
If this is not your issue, you can probably solve it by turning off Name
AutoCorrect and decompiling. Then use only Access 2000 to make any changes.
If you have multiple users with different versions, split the application.
For info on the Name AutoCorrect problems, see:
Failures caused by Name Auto-Correct
at:
http://allenbrowne.com/bug-03.html
To decompile, enter something like this at the command prompt while Access
is not running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
For info on splitting, see:
http://allenbrowne.com/ser-01.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Donald Grove" <do*********@verizon.net> wrote in message
news:jt********************************@4ax.com...
I am suddenly getting this message. It happens during code executed
from a form module that calls a function stored in a standard module.
I am working on a standalone pc with no network connection to
anything. After this message, access closes. Then when I go back,
all the module have been deleted from the form.\
MS error reporting sends me to a web page that says there isn't a fix
for the problem and that I should get Access 2003 (I am using access
2000)
So far I have avoided this happening repeatedly by sticking all the
procedures and functions directly in the form module.
What the hell is this?