sd said:
Split the data base into FE/BE so if one person is in design mode on his FE,
he's not affecting the others.
Yes, this is new with 2000 I think.
from the question
We just converted to xp from access 97 and it is locking the database if
someone is in design mode. Is this new or is there a way to get around this.
The database is shared and not open exclusively.
Yes, access XP is the same as access 2000. You can't modify the application
while users are working. On the other hand, I don't know of any competent
developer that would ever attempt that anyway.
So, yes, split the database, and then you can work on a copy of the front
end. Your testing and development will NOT impact or damage the current
data. In fact, what is great about a split arrangement is that you can make
a copy of the backend data and link to that. That way, you can test all
kinds of cool updates and editing features with out touching the production
system. After all the testers, quality control people, and the usability
testing teams are done and happy with the results, you can then deploy this
new version to all users. Of course, in the case of ms-access, most of the
time you are the development team, the testing team, and the usability team
are all you!. None the less, the split arrangement does give you much
freedom to make mistakes, and work on a copy of the application while users
work away on the current great version.
You also DO NOT want to have multiple users in the same from end. So,
splitting also means that EACH WORKSTATION gets a copy of the front end
database...no exceptions to this rule.
For info on splitting...check out:
http://www.granite.ab.ca/access/splitapp.htm
http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm