Hi guys,

I'm so confused... I have a Linux file server where I am housing a Microsoft Access Database. I have 5 users who needs to access the database at the same time but only one cilent can open the file at a time. I'm pretty sure that the problem is with the permission. When an access database is open, an "ldb" file is automatically created. Thats where the problem start because the by default, the read and write permission is only granted for the user but not for the group.

I think the problem will be solve if i can set the default permission of the newly created files to have read, write and execute permision. I dont know how to do it. Please help..

Thanks in advance!

'man umask'

If I understand your question correctly, I suspect that the problem might well reside within the MS Access protocol itself and won't be an issue you could resolve with server-level permission sets. I think that Access (like Excel) will automatically lock a file while it is active with one user. A second user might be able to access it read-only at the same time, but that would be it. I don't think that using MS Access is a real-time multi-user application, but I stand to be corrected. You might want to look into this before fiddling with user and group permissions on the server.

That is true with excel but i think not in ms access. Before when the database is in Windows, all my clients can access the files at the same time.

What protocol are you using for this functionality?

I really don't think the current Linux compatibility with Access databases is high. I suggest that you use Windows if Access is the only database system you will use.

tcpip is the protocol.

right now, once a user open a database i chmod the file that access created so that all users can access it at the same time. i think umask will help.

is it possible to umask a certain directory? i think my problem wil be solve if only all new files created will have a default 777 permission.

I recently set up a Centos 4 file server for a small company. Op_locks must be disabled on both the Samba server (smb.conf) and the Win clients. Microsoft calls it 'write behind cache'. I tend to think of it as 'he who gets there first wins.' Access and Quickbooks need this done for a multiuser environment. I will try to look up the exact registry values for the win boxes. Try Samba.org to see an example of opportunistic locks = xx in an smb file. Battery low = gotta go. gary

zapatengo! THANKS! IT WORKS! I edit some lines in my samba configuration and it works! Thanks all guys!