multi user access

[northernbreaks]

Hi
If I want several users to access a database from their network pc's, should I place the access database .mdb file on the server and set the Sharing properties, then install the access application on each of their stations.

They need to each be able to use the database when they need to and read or add data, reports etc.

I am using access 2003.

Thanks

Dave

 

[Oldsoftboss]

Each PC will require Access. Create a split database. Put the backend on your server and a copy of the front end on each PC. Each user will then be able to use the Db freely.

 

[fmontana]

upsizing wizard or split the database between front end and back end

what you need to do is import the contents of the table to a new database, save to a central location where all the other computers can access i.e. server, go back to the original file and delete the tables ( Backup before you do this please), and then right click while on the table screen and link (DO NOT IMPORT) to the database on the server. you can only link to tables.

Once completed, you will have a basic client server access database, the database engine will sort out record level locking etc. copy it and paste this client database on all the other clients. Note: if you need to make changes to queries, forms or reports, you have to copy the changes to all the clients. it will be a good idea to do this procedure when you are completely happy with the user (Client capabilities), if it is in development stage, make sure your version you releases so that you can track of what is new and what isn't otherwise you will go nuts with it all. Also make sure you keep a design master. Good luck let me kno if need any further support

 

[northernbreaks]

Multiple access users

Thanks guys, your input is much appreciated.

Thanks

dave

 

[ptaylor-west]

Update please

I read your posts with interest, the only problem I have found is that you cannot link to an FTP server - it is reported elsewhere. Are there any other type of servers available to Joe public that would work?

The only alternative that someone suggested to me was to upsize to MySQL which I have a facility to do so but it seems extremely complicated to do so and I'm not sure I would have the skills to design and make the updates quite so easliy as I can in Access, even though I only do failry basic stuff.

Any advice/ guidance would be greatly appreciated.

 

[complexx]

when you guys talk about front end / back end stuff are you implying the front end includes the user interface while the back end is composed of the tables?

 

[ptaylor-west]

Basically yes - it allows you to change the forms etc without distrubing the data, works really well.

 

[ptaylor-west]

In addition you can split an existing database into a front and back end, but keep a copy of the origional while you test this out.

 

[complexx]

OK. Sounds good. I think I"m going to apply this to the company I work for. This way I can protect the data from the users, lol. I know it sounds funny to say that since they are the ones modifying it, but I don't want them to accidentally be able really mess things up like renaming fields, or possibly deleting tables, etc.

 

[beyer]

I have (in the 90-ties) created a DB for internal use in our department and pasted it on a server, now situated at our Head Office (in another town).
All my users have (now) MS Access 2007 installed on their PC.

Up till now, I have distributed (or the users have created) shortcuts to the DB-file on the server. However, this "shortcut-distribution" turns out to be un-stable (does not link to the latest updates). I do not now why.

I now advise my users to start MS Access 2007 on their PC and open the mdb-file on the server.
÷

• User B and C will not get data updated by user A before he/she has saved his/her changes (like it has been).
• I have to close access to the application to make design-changes (like it has been).

+
No need for split in BE, FE



Some suggestions for smoother solutions?

• E.g. how I can see who is using the DB so I can notify them and ask them to exit from the DB when I want to make design-changes? I assume that users that try to access the DB when it is edited by my, will not be let inn (as it is today).
• Is it posible to create a field on the startup menue that tells last changes in data and by who?
• Other?

Krs & TIA

 

[DCrake]

This is an addition to an old thread but it is imperitive to split mdb's or you will eventually encounter corruption of some kind.

 

[SOS]

No need for split in BE, FE

ALL Multi-user databases (and I'd even go so far as to say for individual users) NEED to be split. See here for why. If you don't split and have the frontend on the user's machine, you are playing Russian Roulette with corruption, plain and simple.

 

[ptaylor-west]

The comments made by Paul Taylor-West on this thread is not me, someone has hijacked my name!!!!!!!!!!!!!!!!!! or the system is corrupted

 

[SOS]

The comments made by Paul Taylor-West on this thread is not me, someone has hijacked my name!!!!!!!!!!!!!!!!!! or the system is corrupted

You mean you didn't make the statements back in 2006? There are none attributed to you since then, it was someone else posting here if you take and look closer.

 

[ptaylor-west]

Definitely not me - I don't know anything about FTP servers

 

[beyer]

Thanks, I'll inquire into that.

Krs