in message:
After setting user security on a database I can not change the database
properties.
When I go into file, database properties and change the title, I am told
Microsoft Office Access is unable to save the database properties.
Yep, I've seen this personally myself..
Only remedy I found was to import all of the database objects
into a new container. Apparently something became corrupted.
MVP Dirk Goldgar once told me that he saw this when:
The only time I've seen anything like it was when I was working on a
database in Access 2000, then copied it to my laptop and took it with me
on vacation, where I worked on it using Access 2002, but without
changing the database file format. As I recall it, I had stored some
information in the database properties when I was working in Access
2000, and then I modified the property when I was working under Access
2002. When I returned home and copied the updated version back to work
on it with Access 2000 again, I found that I could no longer access the
database properties, and there was no way to recover them.
It turns out that A2K and A2K2 store the database properties in
different locations in the database file, and if you let A2K2 store the
database properties, you won't be able to read them from A2K -- at
least, that's the way I remember it. I was quite upset about the fact
that one can effectively lose data this way, with no warning that
anything of the sort could happen. When I complained to MS, however,
the answer was "This behavior is by design," which is their way of
saying, "Whether it's a good behavior or a bad behavior, we have no
intention of changing it." I was not happy
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)