Splitting a Server Hosted Access Database -


I am looking at creating an access database that will replace the very fierce coincidence of the associated Excel spreadsheets. The files for the current spreadsheet system are located on our Windows Storage Server, in which they are the mapped drive to the directory used by them. More than one user uses this system as this because they create an inventory, pricing for the materials and prices used for each product. I believe that using a database is a great idea. As I see it, if I divide the database it will give me a front and back end. Allow multiple users to enter and make changes at the same time, with out corruption! Woo-hoo !!!

Is that correct? And has anyone applied it? Did the end users easily access the database? There is no problem with this which I had not seen. I have read that users can have a front end locally on computers, is this true / good?

Access works very well for small offices, if it The database should be divided properly, each user has a copy of the front-end. This does not mean that every user requires a complete copy of access, the runtime version is sufficient. 2007 Runtime is free ()

You should read this thread which deals with many misconceptions:


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -