Was working in A2003 and noticed that the Save Record item on the Records
menu was not available when the record was not dirty. In A2000, Save
Record
was always available. (This is a problem for me because I have
Docmd.Runcmd
acCmdSaveRecord code all over the place, which never gave an error before.
But now it was giving an error when the Save Record menu command wasn't
available.)
So I went back to A2000 and confirmed that the Save Record menu command is
always available, whether the record is dirty or not. So I concluded this
was a change in A2003, that the menu item's only available when the
record's
actually dirty.
However...... when I went back to A2003 and tested it again, I noticed
that
it was acting in the same way as A2000, with the Save Record menu item
always available!
So, in summary:
In A2003, Save Record menu item was only available when record was
actually
dirty (causing an error when docmd.runcmd accmdsaverecord was run when the
record was not dirty).
Went to A2000 and confirmed that the menu item was always available,
whether
the record was dirty or not.
And when I returned to A2003, all of a sudden the menu item was always
available, as it is in A2000, though a few minutes before it had only been
available when the record was dirty!
So I was wondering if anyone else has noticed these shenanigans from
A2003,
or has any idea what's going on, and why the funcationality would change
like that. Also, how does A2003 act in your copy: is the Save Record menu
item always available; or is it grayed out when the record's not dirty?
Thanks!
Neil
|
