2950? Ah right - I see... Macros forum. But you're presumably calling a VBA function in this macro?What function?Since it's only started giving you an error (i.e. you've changed nothing?) then corruption is one likely possibility.And a decompile would be appropriate.Also it might be related to a trusted issue (the project you're running isn't trusted).HAs described in this MS article.

Many thanks for replying. I have already had a look at the trusted issue thing and I am confident that this is not the issue as I have enabled all macros and added all locations.The problem function seems to be 'openform' - by the way I am relatively new to everything Access!!

Don't worry - I'm on wobbly legs myself with Macros. ;-)o the application is definitely in a trusted location? Your code is able to run normally. (i.e. if you run a VBA procedure without using a Macro - it completes normally - and visibly?)Have a look at the decompile method mentioned then. Just to be sure.

Certainly.The easiest way is probably to make a shortcut.But you can do this from a command prompt or Run it.For example in the Windows menu Start> Run >Ultimately you'll want a path such as "Path to MSAccess" /decompile "Path to your App" For example:"C:\Program Files\Microsoft Office 2007\Office12\MSACCESS.EXE" /decompile "H:\Apps\MyApp.ACCDB" That run, either from a Start prompt or as the path in a shortcut.You can equally run it from VBA of course.Shell """C:\Program Files\Microsoft Office 2007\Office12\MSACCESS.EXE"" /decompile ""H:\Apps\MyApp.ACCDB"""

OMG OMG OMG, you guys saved my life. I built the customer service for the entire company around this stupid database in access and I got this error today. It wouldn't let me pull reports, forms, or print. It would have been a massive undertaking to rebuild it if I couldn't find the error. I clicked on VBA, Debug, Compile and it worked like a charm. It even fixed another random error I have just been living with all this time. Thank you so much...and god bless this forum. LOL

Seems to have worked for a problem I was having, too. VBA --> Debug --> Compile is a life saver! I would have never thought to try this, as I am only using macros and haven't written any VBA. Thank you UtterAccess!

If you are a "belt AND suspenders" type, make sure you have regular backups of the entire db/application. That way, if the Compact/Repair or Compile or /Decompile fails to fix the problem (or just plain fails), you still have a most-recent backup... and if you are a "belt, suspenders AND a length of cord" type, make a backup every time you tell yourself "whoa, I sure wouldn't want to have to do all THAT again!".Good luck!