Save command produces error in MDE, not MDB

[Guest]

I have an mdb that works flawlessly, but when I compile it into an mde, I get
an error every time it encounters the "docmd.runcommand accmdSave" code. I
get "the command save isn't available now."

Any ideas? I can't find anything on the web. Thanks,

 

[Brendan Reynolds]

That command saves design changes, and you can't do that in an MDE. If you
want users to be able to make design changes, you need to give them an MDB.
If you intended to save changes to data rather than design changes, use
acCmdSaveRecord.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

 

[Graeme Richardson]

I'm guessing here but I think that docmd.runcommand accmdSave statement is
attempting to save the active object (a form or report?) which is never
available in an mde.

If you mean to save changes to a record then use Me.Dirty=False

HTH, Graeme.

 

[Guest]

Both of you, thanks! Duh.