Diff between using the Db Splitter wizard and just linking tables??

[istuart]

I actually have three questions....here goes.

First, I have a database in a multiuser environment. It's a small environment, so all of the users have full access. I created another database (also for multiusers), for the purpose of searching data only. The users have the ability to search records (I created a form from a query) or run three different reports. No data can be entered, changed or deleted in this db. Now comes my question...Rather than splitting the database with the wizard, I linked only those tables where the applicable data resides. I did this through File -> Get External Data -> Link Tables. This seems to work fine...but want to know if this was the most efficient way to do it. What are the implications of not splitting the database?

Next question...I have both databases on the same drive...but not all users have the same drive letter available on their computers. I've seen other threads that suggest using UNC ...but don't understand how to set this up.

Finally, I am testing the database using two computers (mapped to the same drive letter). I have specified that it is a shared database under both &quot;Options&quot; and &quot;Database Security&quot;. The problem is that only one user is allowed access at a time. The first user to enter the database is the only one allowed access. Additional users get an error message...Couldn't use <name>; file already in use (Error 3045). Urgghhh?!!

Any help is greatly appreciated.

 

[ryan1]

First I link all my tables works great that way.

Second when you link tables you must remember that not all user use the same drive letters. You must link the tables buy going through the server. For example go to network neighborhood/domain/server1/folder/example.mbd. As far as file already in use error. Need to check user access to folder were the data is stored. Users that access the database must have change access to the folder where your tables are stored. Also check to see if you have Eidted record locks on this could also cause multiuser errors. There are ways around using edited record locks to lock records.