Hi
Thanks for the reply.If in mean time if you get you know any other options please let me know
Thanks in advance
Dilip
QUOTE=Jim Doherty]Hi Ramdil,
In addition to what owyn999 says you give the user their
own file not the shortcut to a single frontend file. You are not splitting it in the spirit of things because one frontend file is being accessed 17 times concurrently potentially and that is where any locks will be taking place in one ldb file on the server because some user or another has eited out wrongly or improperly or a simple network connectivity glitch. I have recently mentioned the same thing to another thread. If you are able to install the frontend file on the client then do so because that way you are running each file then 'per user' under its own steam on the clients installation of Access
http://www.thescripts.com/forum/thread745608.html
In addition you are not having to drag the a potentially uncompacted high megabyte file over the network when they double click to open it, A local copy can open up locally to that client machine. The downside is 'distribution' of not having the frontends located conveniently on the server accepted but you could create a logon.bat at network user login to download the latest version from the server to the client. or write into your app version control to deal with that when it opens. Its whatever suits our networking arrangements.
Regards
Jim :)[/quote]