Access On A Network

[statsman]

For the past several years I have been designing and building Access databases. They are designed for small evironments to be used on one machine only.
I am now faced with a situation where my client would like to have his database placed on his network server so it can be accessed by several computers.
This is a little outside my area of expertise.
I have searched the forum but I keep coming up with references to front end and back end and other things I don't understand.
Can someone point me in the right direction to search for:
what should be on the netword and what should be in the computer.
what changes should I make to the database stand-alone vs. network.
what unexpected problems should I expect.

Or perhaps you could suggest a book I could buy to assist me.

Many thanks

 

[RuralGuy]

Maybe this link will get you started: Split your MDB file into data and application

 

[cross5900]

Basically the backend of the database is just the information and no form of GUI(forms).

The frontend is the graphical part with the user in mind using linked tables from the backend source. Fortunately Access is designed for multiple users so you do not have to work about the network part, just make the dbase, with a backend/frontend and you will be good to go.

 

[statsman]

Thanks, very helpful.
I assume the "backend" is the tables and the "frontend" is the forms, queries reports etc.
The "backend" goes on the network and the "frontend" goes on the individual computers.
Am I correct?

 

[RuralGuy]

Absolutely correct! You've got it now.

 

[lasatalayas]

I've done this many times on a local area network and also using routers across a Wan.
But can it be done with the tables on a Web Server and the Access front end on users web connected PCs?

 

[RuralGuy]

My guess is you will *never* be satisfied with the performance and I'm not sure you can do it that way anyway. Using DAP's maybe.

 

[lasatalayas]

DAP's ?
What are they?

 

[RuralGuy]

Data Access Pages. This should really be a new thread!

 

[iangirven]

statsman,

I have had my database split into front end with the backend on the local server and its been running for over 5 years now without any real problems. However you do get the odd glitch now and again when one of the remote users had locked the db. If you keep regular backups of the backend its usually easy to resolve.

You will notice a drop in the performance of the db which will depend on the quality and bandwidth of the network but i think its worth it for the extra flexibility of working across the network.

Good luck and keep us posted on how you get on.

regards
ian

 

[statsman]

Worked great. Thanks to everyone.

 

[statsman]

Sorry, forgot somthing important.
I have two folders which contain the OLE objects for the forms.
The first is for Excel spreadsheets. The second is for .pdf
Should these be placed on the front end or back end.

Thanks

 

[RuralGuy]

Putting them with the BackEnd would make it easier to maintain. Putting them with each copy of the FrontEnd would make them load faster. There's always some sort of trade off.