J
\Jonathan Scott via AccessMonster.com\
I had a user open a table through the database window at the same time they
were editing it in a subform. It seems to have caused an error in a field in
the table which was resolvable only by erasing the entry and recreating it.
Otherwise, even just mouse-overing it would cause an error stating the field
was already locked by someone else.
My assumption could be wrong, however, to help narrow down the possibilities,
and keep abnormal behaviour to a minimum, I would like to disable the
Database window entirely after rollout. I've looked at these "hide database
window" posts, but they don't actually disable the window.
Is there a way to disable the Database window?
Jonathan Scott
were editing it in a subform. It seems to have caused an error in a field in
the table which was resolvable only by erasing the entry and recreating it.
Otherwise, even just mouse-overing it would cause an error stating the field
was already locked by someone else.
My assumption could be wrong, however, to help narrow down the possibilities,
and keep abnormal behaviour to a minimum, I would like to disable the
Database window entirely after rollout. I've looked at these "hide database
window" posts, but they don't actually disable the window.
Is there a way to disable the Database window?
Jonathan Scott