Microsoft Access across a office lan/Intranet

[Guest_imported]

OK my problem, a client wishes to have a client database of their own on their system. I haven't commited to anything yet but i think Access will do the job. I know exactly how to build the database. My problem is how to install it across a small office network. How would i have to go about installing the program?

Thanks for your help!

 

[hermanlaksko]

1. split you base into a front (yr prg) and a back (the ac. database).
2. Connect the 2.
3. Install as run-time or if they have access on ther PC's copy yr prg to the PC and yr back to the server.

Herman

 

[comtaxdog]

You may want read the MS white papers on workgroup security also. There are many concerns while running Access across servers and in multiple users situations. I'm doing it now with a split database, workgroup security, programming and static tables in file on several servers across the country and linked to tables on a main server. You will also need to work with the Network Security people to install a short cut icon that allows the client not to be permanently attached to the file tree.

 

[Guest_imported]

I'm thinking Access for the backend and VB for the front end.
But the client wishes all terminals (5) to be able to edit records at the same time. Are there any problems here?

Can I do this with only installing Access on the server?

Any info is appreciated!

ComTaxDog - Theres to real security issue all the users will be accessing the one file.

 

[Quehay]

I've had over 90 instances of Access db's in a company LAN setting--with good results.

1. Make sure you've got backup for servers. Mdb's corrupt at a moment's notice and you don't want to tell people their data are gone. A split backend may be copied at any time although pending updates wouldn't be included.

2. Split into backend on network server. The front end may be on network if it's likely to change/be updated or on client machines if not (latter is less network traffic).

3. I've just used Admin user (security not activated) and relied on NT security or passwords. Access security is a headache if you don't need it.

4. Use startup properties to secure your front end from "power users". Keep the backend file in a folder that has restricted access (if you link the front end you confer your privileges upon it as db owner).

5. Five users shouldn't be a problem if there isn't competition for updating the same rows. Optimistic locking is much less overhead if you can do it. Jeff Roberts
Analysis, Design, & Implementation
RenaissanceData.com

 

[gusbrunston]

Dear Jeff:

You piqued my curiosity about the "The front end may be on network if it's likely to change/be updated..."

I'm trying to picture this, and my head is empty. If I could put the front end on a small (3 workstations) lan it would sure save time and trouble having to install new front end revisions on each station.

Now how does one go about this?...

Thanks, Gus Brunston An old PICKer, using Access2000. I manage

http://www.rentdex.com.

Suggestions welcome. padregus@attbi.com

 

[gusbrunston]

Well...I guess you just put the front end on the server, map the drive\folder on each workstation and there you are! MS Access must still be on each box. Wouldn't have thought about it without you, Jeff. Thanks.
Gus Brunston An old PICKer, using Access2000. I manage

http://www.rentdex.com.

Suggestions welcome. padregus@attbi.com

 

[Quehay]

Once upon a time I had a scripting routine to check if the front end was running of C: or the Network and then prompt user to run routine that would copy the front end to local drive and create a shortcut for them.

The next step was to script a "LastModified" file property check that would compare the network master copy with the local copy and prompt for an update of local copy if it was out of date.

However life is short and I got less concerned about pulling 3M front end files across the wire. If everyone works off of the network copy then you don't have to worry about stragglers using an old, obsolete copy (not really an issue if you're just supporting < 5 people). This can be done though... Jeff Roberts
Analysis, Design, & Implementation
RenaissanceData.com

 

[Guest_imported]

I've decided to drop VB and go with all access, front and back.

Thanks for your help everyone!