Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Multiple users can't share MS Access file on linux server using Samba

Status
Not open for further replies.

BLH1

Programmer
Dec 22, 1999
1
US
I set up a Linux file-server using Samba, and successfully connected multiple 98 workstations to the server. I can share files, but when I try to execute a MS Access database file that is already in use by another user, I get an MS Access error message &quot;Couldn't use db.mdb; file already in use.&quot; Does this have something to do with &quot;record locking&quot;? Can this be remedied through samba config? In addition I tried the above with an Excel file, and ran into the same problem...<br>
<br>
Thank You!
 
I think that what you are running into is known in M$ world as an &quot;access violation&quot;. Taking the Excel example, when user A opens the file it is locked by Windows. User B is not able to access the file until user A exits. This happens in any Windows environment, regardless of what the server is. (Novell, NT, or Samba.)<br>
<br>
Using Access, it is extremely likely that you are running into the same problem. ie, the file is locked by user A.<br>
<br>
To prove this, try the following:<br>
<br>
* Copy the Access files to User A's system.<br>
* Share the directory containing the Access files.<br>
* Have user A open the database.<br>
* Have user B attempt to open the database through Network Neighbourhood.<br>
<br>
If the same thing happens, then the Access database needs setting up as a multi-user database. I don't know how you do this, but I'm sure there'll be an Access thread somewhere on Tek-Tips. :)<br>
<br>
Hope this helps.
 
You might want to just give each user a diff. name for the file(s) in question and set up a shell script to run in the backgroud (i.e. in a minimized terminal window) to lone the files every 2-3minutes so everyone gets the same, fresh data even though they'r accessing diff copies of the file. (might want to make the script copy whichever one has been most recently updated if it's likely to be changed though). <p>-Robherc<br><a href=mailto:robherc@netzero.net>robherc@netzero.net</a><br><a href= > </a><br>*nix installation & program collector/reseller. Contact me if you think you've got one that I don't :)
 
HAVE YOU SET UP EACH USER TO POINT AT THE SAME WORKGROUP ADMINISTRATOR FILE -LOAD THIS ON THE SAMBA SERVER AND USE WKADM.EXE ON EACH MACHINE TO POINT AT IT.
 
Thanks for the help but the solution was quite simple, all I needed to do was add the line
 
I just read this thread -- a month late -- because I think I'm going to have the same problem soon. I would love to know what the solution was, but all I can see of the final message (from blh) is:<br>
<br>
Thanks for the help but the solution was quite simple, all I needed to do was add the line<br>
<br>
It ends there, but what was &quot;the line&quot; that was added?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top