is it possible to create a Multiple User Access Database??!?

[Guest_imported]

I have a database with lots of forms etc...how do I make it so that multiple users can use the database at once. The database is on network (Windows NT). Also, is it better to have your database linked to tables? I have everything now in one big database, there are lots of tables, lots of forms etc...I also hear Access databases have a tendency to crash? Any info about this and possibly how to lower the chances of this happening...

Thanks

 

[GingerR]

you don't have to do anything to let multiple users use the db at once. It's already made for that. They just have to open it.

make sure if your users are entering or editing data that you have record-locking set. look in the properties of the forms and make sure for RECORD LOCKS it is set to EDITED RECORD. this prevents more than one user from editing a single record at the same time, a big reason for crashes.

there are lots of reasons for crashes, in my experience it's been mostly what i said above, which was my fault and doesnt happen any more cause i know better. other reasons can be network issues (network down) but that doesnt make the db crash, just makes it unavailable.

'crash' = people can use this when really there are just code errors. users will call you with funky error messages which you will figure out the reasons for, fix the code, and never have it happen again. that's just the nature of any program beast.

as for the FRONTEND + BACKEND (linked tables) issue: most of us do that i'm sure. you can provide a desktop shortcut to every user which points to the FrontEnd database on the server, and that is fine. I only do that when users are only viewing data/reports, etc, not actually entering or editing data. When there will be entering data, editing data, more intense programming going on, i write code that puts the front-end onto each user's machine, and a desktop shortcut that points to that front end (which is linked to the backend, on the server, which holds all the data). the advantage to this is that i work on a development copy to change forms, reports, etc as i need to, change the version number in a little table i call Version, and when the user clicks on their shortcut it first runs an administrative db (that also got installed onto their machine) that first compares the version of the front end on their machine with the version of the frontend on the server, and if they are diff, it copies the 'new' frontend to their machine and opens it. this is because you can't change the programming/forms/reports, etc when people are using it. well, actually you can change forms and report when people are in them, but they will not see the changes until the get out and back in again. it all just depends on how many users you have, how much they are in there, if you can walk over to them and ask them to get out so you can make changes or if you will be all freaked out waiting for everyone to get out so you can change something..or if it is too tacky and unprofessional to do that......

so as you can see there are lots of options. if you still have questions, tell us how many users you have, are they physically close to you, will they be entering/editing data, how often, how much....and we can help you make a decision. also, any decision you make now can always be changed so don't sweat it.

g

 

[Guest_imported]

So by making an icon that points to the databas etc...does it make the database move faster? What are the advantages of having two different databases...one with what the users use and the other with the tables (private information) that holds the info....

thanks

 

[GingerR]

making an icon that points to the database does not have anything to do with the operation of the database. it is just a desktop shortcut for your users, so they don't have to browse around the network looking for it. They can click on a pretty little icon (you can have your own cool icon picture you know) to get to the db, then it doesnt seem like such a hack-job and a little more professional.

one of the major advantages is what i listed in my previous post - so you can do development if you need to (in a separate front-end development copy), without having to continually bother your users to get out of the db or waiting until they are all out to save new programming changes. if this is not a requirement then you can just have all of your users using the same front-end on the server, or for that matter, keep it all in one big database on the server and they can all use that. depends on your situation.