Recent content by lepaule

It's not a problem with the user code. It is an internal problem of the MS Access compiler, probably because the code project is stored in a semi-compiled state. It caused me grief in Access 2000 and it is still a problem in 2010 (I can't recall an event with 2013 but I've only been using it for...

The solution, as it has been many times in the past for me, is to decompile. It slipped my mind to do this when the compile function wasn't finding missing variables in one of my modules, so I ended up here. Run from command prompt >> msaccess.exe /decompile "C:\Your Path To\YourDBName.mdb"...