[AccessD] Multiple Frontend Users

Elegant Jim!

Regards
Chris F

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim Dettman
> Sent: Tuesday, May 20, 2008 1:33 PM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Multiple Frontend Users
> 
> 
> Chris,
> 
>   I do that the same, but twist it around a bit; the FE has a 
> version table
> and at startup, checks the local table vs a network "master" 
> copy.  If the
> rev's don't match, the user is told to "update" (run the 
> batch file) and the
> app quits.
> 
>   The batch file also serves as the install as all one needs 
> to do is call
> it from the run line or click on a link in an e-mail.
> 
> Jim.
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of 
> Foote, Chris
> Sent: Tuesday, May 20, 2008 8:22 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] Multiple Frontend Users
> 
> Arthur!
> 
> I've had similar arguments with our IT "professionals"!
> 
> My multi-user split FE/BE database worked as follows:
> 
> BE and copy of FE stored on network "share" along with bat file.
> User has shortcut to bat file on desktop
> When user needs to use database they double-click on shortcut 
> to bat file.
> Bat file looks to see if user has latest version of FE on 
> their C: drive,
> if not, it copies file for network share and runs it, if it 
> is latest it
> runs it.
> 
> Simple!
> 
> The only this you need to do if user gets a new machine is to 
> create the
> shortcut to the bat file. I would have automated that if I 
> could have been
> bothered ;-)
> 
> If you need any more info of a copy to my super-duper bat 
> file please let me
> know.
> 
> Regards
> Chris Foote