7 replies
by sl-campbell
There are no real problems with this unless the users are modiying the same record at the same time.
You need to make sure that the users have permissions to edit the objects, (usually this is the default), and that any database or recordset objects in code are opened for shared usage, and that the standard open mode option in MSAccess is set to shared usage (also default).
What exact problems are you having?
by sl-campbell
Donq is right. I guess I read it too fast and didn't see that the problem was more basic.
However I would suggest not using the database splitter if you have alot of tables.
I would open an empty database and import the tables from the original and then move this to the server. Then in the original I would delete all tables and then link all the tables from the new mdb which is on the server via 'File / External Data / Link Tables' (or whatever it is on the english version). Do this for the 2nd workplace also, or copy the linked MDB and refresh the links.
With the splitter, when the number of tables reach a certain amount (with my experience somewhere between 80 and 110) the linking information is not always 100% correct. You will notalways experience a problem (and maybe not even via Access but thru another program when accessing the linked tables- such as Crystal Reports).
On MDBs with a small number of tables I never saw a problem using the splitter, and manually creating the links I never had a problem no matter what.
by sl-campbell
Did this answer your question?
by bobby
by donq
by bobby
by bobby
This discussion is closed to new replies.
Trending Web Development posts
Sort by Trending