To All,



Original Question: Access Database on Novell Server, 5 have admin 

permissions, 45 read & write only. When changes need made I am locked out. 

The responses suggested using the "database splitter" in Access to store 

the tables on the server, and the forms and such on local machines.



The follow-up to these suggestions of splitting the database into stored 

tables on the server, and forms/queries/reports, etc.. on everyones 

machine, is:



What happens when I want to modify a form? Do I have to make the 

corrections on all 50 machines running this part of the app? Once it is 

split, it is split right...?



Regards,



Tom

Yes, you will have to update the front-end wherever your users 

are accessing it.  If that's a single, shared file on the server, 

then you'll have to chase them all out of that & then filecopy 

your new version over top of the existing one (and now that 

there's no data in the front-end, there's no data to lose--

everything in the FE belongs to you). If you've set up your users 

each with their own copy, then you'll have to update each copy.



The down sides to having a shared front-end are:



1) You've still got to chase your users out of the app in order 

   to do updates.

2) Slightly(?) worse performance than you would get by giving 

   everybody their own copy because:

	a) you're pulling forms, reports, etc. over the wire, and

	b) access will spend time creating and monitoring a record 

   	locking database file (.ldb file) for both the front-and back-

   	end files, even though there's no data in the front-end).

3) No good way of having user-specific temp tables.



The obvious down-side to having individual client-side FE files 

is that they've all got to be updated individually--and that opens 

up the possiblility that not all of your users would be running 

w/the same version).



I'm lately going w/individual FE files, b/c I had an app that had 

serious performance problems & I was forced into it.  



In order to deal w/the hassles of the updates, I wrote up a 

VBScript installer that puts two shortcuts on the users' 

desktops--one for the app itself, and another for a second 

vbscript that does a filecopy of the FE file from a central 

location on the server to the appointed location on the user's 

machine.  When I make an update, I send an e-mail out to the 

users asking them to kindly 'refresh' the application at their 

convenience.  It's working pretty well for me so far...



HTH,



-Roy





-----Original Message-----

From: T.Benjock@w... [mailto:T.Benjock@w...]

Sent: Tuesday, August 21, 2001 7:13 AM

To: Access

Subject: [access] FOLLOW-UP to Access User Level Locking !!





To All,



Original Question: Access Database on Novell Server, 5 have admin 

permissions, 45 read & write only. When changes need made I am locked out. 

The responses suggested using the "database splitter" in Access to store 

the tables on the server, and the forms and such on local machines.



The follow-up to these suggestions of splitting the database into stored 

tables on the server, and forms/queries/reports, etc.. on everyones 

machine, is:



What happens when I want to modify a form? Do I have to make the 

corrections on all 50 machines running this part of the app? Once it is 

split, it is split right...?



Regards,



Tom