Question Installing an Access Database on to a server

[Tumby]

I have created a database which needs to be installed onto a server running MS Small Buisness Server with 4 PC's connected to it.
Does access have to be installed on all the PC's connected to the server, or just on the server.

 

[KenHigg]

Install it on the local workstations. The Access database file with the tables need to be placed on the server.

 

[Tumby]

Thanks KenHigg- I new the actual database would have to be on the server.
But to know that Access application only has to be on the server is great- saves LOTS of money!

 

[KenHigg]

Hum... Maybe I wasn't clear. MS Access does need to be installed on each workstation. But you can just load the free MS Access runtime version to keep from having to spend a lot of money.

 

[Rabbie]

If your DB will be used by more than one user at a time you should give serious consideration to splitting the DB and having the BackEnd on the server and each user having the FrontEnd on their own PCs. This helps to prevent data corruption.

 

[KenHigg]

I'll yield to the resident expert from here -

 

[Tezcatlipoca]

I've got the exact same situation running on a server at work. The database is split into front end (an MDE) and backend (and MDB).

Back end goes into a shared folder on the server, to which all client PCs have access and full rights. Access is NOT installed on the server.

Front end goes onto the client PCs (one copy for each), and the linked tables automatically tell the database to look for the back end on the server path. Access IS installed on each client PC.

Hope this helps.

 

[Tumby]

Thanks Tezcatipoca, that is great info.

When the datbase is split does it generate the linking files? OR am I being plain stupid.

My clients are just evaluating the datbase on one PC but when they are satisfied with it, they want me to put it on their server. Four PC's will be using it, 2 regularly the other two occasionally.

Thanks also to everyone who has given me advice.

 

[KenHigg]

When you create a simple Access database you create everything in one file. The tables, forms, reports, etc. It's fine to leave it like this if you are only going to run the database from a single computer. But if you want to run it from several computers you create the tables in a seperate Access database file and put this on the server. Then you put a copy of the other Access database file, the one with all of the other objects like forms and reports, on each workstation. Then you open that file and attach to the tables in the file on the server.

Hope that makes sense -

 

[Tumby]

Thanks KenHigg makes sense now!

 

[SimonB1978]

Hi,

I don't want to hijack Tumby's thread, but I read that you all suggest having the back-end on the server and the front-end on the user's PC. Besides the obvious bandwith usage, is there a reason not to have the MDE also stored on the network? I think it makes updating a lot easier...

Thank you,

Simon B.

 

[Simon_MT]

Not good. Even with faster ethernet speeds, all the MDE is asking for is the data, if the MDE was on the network the every object would be over the ether. More importantly ther server is a dedicated resource with a specific functions and has more pressing issues than running databases. Any administrator might have a few to say! The exception is a Terminal Server for remote users.

Simon

 

[KenHigg]

I had one deployed like that and it ran fine for years...

 

[Simon_MT]

Yes, it will work but it is more efficient on each PC with a Front End and a server based Back End.

Simon