Determining the best front-end distribution scheme

[mguidry5]

Hiya,

I've developed a small database that will be used daily with the potential for four users to be in the database at once. I have a custom workgroup created and users will only be able to access the database from a shortcut that specifies the workgroup. The database has not yet been split, though I'm almost certainly going to prior to distribution and implementation.

I'm wondering what the best distribution method would be. Each user will be working in a separate set of forms, and there will be no record-lock issues because they only have write access to records they've created. Would it be acceptable to allow all users to access a common frontend on a network location, or should I distribute the frontend to the local computer(s) that will be used to run the app?

If you have any suggestions or caveats, let me know.

Thanks,
Mike

 

[markphsd]

For multiple users distribute the front end. You will have to learn how to, but it's the recommened method.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[LittleSmudge]

Splitting FrontEnd and BackEnd is a MUST.

Do it on the day you first sit down and start working on the Db - it's a lot easier than waiting until the day before production launch !

But given the position you are in Do It NOW.


Then put the BackEnd in a common accessable location on the network, put the Security.MDW with it.

Link the FrontEnd to the BackEnd making sure that you use \\Server\Path referencing to avoid LetterDrive mirror errors caused by differences between machines.

Then put the Front End in a common location on the network and develop a method of copying it to each user's C: drive.

I tend to create a DBs folder in their C:\Program Files folder and all their FrontEnds go in there.

Then the user's shortcut simply runs the file on their C:\drive and the only network traffic is the data from the tables.



'ope-that'elps.




G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.

 

[alvechurchdata]

Splitting FrontEnd and BackEnd is a MUST.{/quote]

No excuses. Do it.

You'll be really grateful when one of the users upgrades to a newer version of Access. You can upgrade their front end and let it share data in the old format with everyone else.

I've got a system where the data's in Access 2 format and it's being shared by users running all versions between 2 and 2003.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[markphsd]

See, it's the recommended method

In fact, you might want to learn how to move it over to sql server.

Mark P.

http://www.cafecartel.com

Providing Low Cost Powerful Point of Sale Solutions.

 

[psemianonymous]

Splitting the frontend is a must, if only so you can do development on the frontend (ad-hoc reports and whatnot) without the REAL hassles of doing this while 4 people are using it.

Sometimes it's ok to leave the frontend in the network share if your application is informal enough--and for me it usually is. It isn't totally necessary to push each client an "updated frontend" for a marginal performance boost--it's a lot of hassle. I say, do it after your users experience problems, not before.

Check out my FAQ about multi-user Access:
How many (max) users can Access support? faq181-4462