Allow change to backend form/macro/query when frontend db open

[Guest]

With Access 2003 I can't save changes to the backend database if anyone has
opened a frontend database with linked tables. I can understand this for the
tables that are actually linked, but why for tables not linked and why for
forms, macros, queries, reports ???

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...7797&dg=microsoft.public.access.modulesdaovba

 

[Guest]

oldgeezer,

My first question is why do you not capitalize your name? Can't get it up
anymore
I have a right, I'm older than anyone!

As to your problem. The first thing is there should be no forms, macros,
queries, or reports in you backend database. Back End databases should
contain only tables. Also, Exclusive access is required to make changes to
an mbd. That is why you can't change even tables.

 

[David C. Holley]

kLATUU...
I would not entirely agree with the idea of a backend only containing
tables. I would QUALIFY that by saying that if the backend contains ANY
forms, macros, queries and reports that those objects should be the ones
for exclusive use by the DB administrators.

David H

 

[Guest]

If it could be justified, I would accept it; however, a separate admin
database might not be a bad idea. One consideration is that if you have
objects other than tables in your BE, then upsizing becomes more of a problem.

 

[David C. Holley]

True.

If it could be justified, I would accept it; however, a separate admin
database might not be a bad idea. One consideration is that if you have
objects other than tables in your BE, then upsizing becomes more of a problem.

: