[AccessD] AXP Question

Terri,

One of the good features of A2K and higher is that you no longer can
make design changes while others are in the app.  Some may disagree with
this, but it has been a sound development practice since the dark ages
of computing that M$ finally implemented.

I always keep a copy of the current production FE on my PC and develop
my changes on it.  When I am ready I then replace the production copy
with the new version.  If the users go home at 5PM, then I do the
replace after 5PM.  If the users work 24/7, then I have to get them to
sign off for the few minutes it takes to do the replace and then they
can sign on again.

Charles Wortz
Software Development Division
Texas Education Agency
1701 N. Congress Ave
Austin, TX 78701-1494
512-463-9493
CWortz at tea.state.tx.us



-----Original Message-----
From: Terri Jarus [mailto:jarus at amerinet-gpo.com] 
Sent: Friday 2003 Jun 06 07:27
To: accessd at databaseadvisors.com
Subject: [AccessD] AXP Question

I have upgraded a FE database from A97 to AXP successfully,  however, a
major difference that is annoying me is the fact that in a multiuser
environment, I am unable to make changes to the design unless I open
exclusively.

I never had this problem in A97 and now that my users are all getting
upgraded to the AXP FE, I am running across a few areas that need to be
tweaked and can't do it until everyone is out of the db.  This is a
shared network FE.

I should probably give everyone their own copy on their desktop,
however, this database has evolved greatly over the past 3 years and has
required many changes.  I have always been able to make these changes
while the db was being used by others with no problem.  There are about
20 users - so upgrading everyone's FE would be very tedious.

I know there are some automated programs to do the updating, but one I
had tried took too long and was cumbersome to the user.

Any suggestions or ideas - is there a setting I'm missing that would
allow design changes while in use???

Thanks for any help.