A-2000 'Object not supported in transactions' when Compacting

[JimHorton]

Has anyone recieved the above error message while compacting an A2000 mdb? I'm doing my first 'real' project with 2000, and I'm getting this message. <br>
<br>
Also, I'm seeing some odd corruption: I renamed several forms and their subforms. Now, I continuously (that is, whenever I try to save *anything*) get the error message &quot;The name '[my old form name]' is either misspelled or refers to an object that doesn't exist...&quot; Apparently this is because the form is gone but the vba code module for it was not removed by Access, and this problem will *not* go away, the 'remove module [old form module]' option is greyed out. Anyone seen this? I checke MSKB on some of these keywords and couldn't find anything. Thanks,<br>
--Jim

 

[elizabeth]

Just a thought - you might try creating a new form by the same name, and see if that lets you delete the old module or deletes it when you change the HasModule property to No or delete the module a second time.

 

[JimHorton]

Thanks, Elizabeth. I tried that, and when I'd attempt to go into an Event module, I'd click the ellipsis next to the Event and it would do nothing. It's a strange problem. Then I'd close the form, and if I said Yes to the 'do you want to save..' prompt, the Yes button was dead--nothing happend. At other times, I'd get the message 'the save operation failed'. So, I just started from scratch, and tried importing some of the objects I thought were 'safe', one-by-one. Then, I came to one that had an error something like