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

--
Message posted via http://www.accessmonster.com

IMHO, the only way to completely disable database window - is to run
application under Access runtime

--
Alex Dybenko (MVP)
http://Alex.Dybenko.com
http://www.PointLtd.com


""Jonathan Scott via AccessMonster.com"" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
>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
>
> --
> Message posted via http://www.accessmonster.com