DB for client-server use

[jayke]

Hi all,

I created an application that I was using at my work. Now other people would like to use it. I would like to have a client-server setup for my DB.
Can I do this by just putting the application on a server? Can a single application handle multiple users?

What if I open a recordset and I keep te recordset open for 20 minutes..
In the meanwhile another user tries to adapt a record. Will this go wrong?

I have read some stuff about splitting the DB. But is this really necessary?
Once splitted I can never go back to the original.

What is the best thing that I can do.

I know security is also important but I just want to know what the best solution is for multiple users on one DB.

thanx

 

[pbaldy]

If you have multiple users, you really should split the db, with a front end on each user's PC and the back end on the server. You could switch back to a non-split db later if you wanted. You would be asking for corruption issues to have multiple users accessing the same file on the server.

 

[jayke]

Hi,

Thanks for your responses.
So splitting the DB is the best thing to do. Ok, I have something about it and indeed it doesn't sound that spactacular.

But what about the .mde and .mdb files? Each users should have such a file to have access to the DB? Can someone tell me more about it?

I can use a splitted DB without them?

thx

 

[puthenveetil]

Hi Pat,

Can I rejoin a splitted be and fe to a single mdb??

thanks

 

[jayke]

Pat,

Thank you!
With the description you gave I can certenly move on!!!


Cheers!

 

[WayneRyan]

puthen,

Yes, you can rejoin them. Just import all of the front-ends objects (except
the linked tables) into the back end. Or vice-versa.

Wayne