 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / New Users / August 2006multiple users
We recently moved an Access database file from a Win98 machine to our main File Server (Windows 2000 Domain controller). When on the Win98 machine more then one user could access the db at the same time. Now only one or two can at the same time. Not always the same users can access it at the same time. I tried it when I first moved the file to the DC and three or four could get on but not now. I even when as far as making the folder that the db is in have Full Control access to all just to see if it was a security thing but no change. The db file is saved as Access 2000 and the users are using 2000, 2002 (XP) and 2003. There is no Access Workgroup security on the file. If you have not already done so you should split the database into front and back ends, the former containing the forms, reports, queries etc, the latter the tables only. Put the back end on the server and a copy of the front end, along with Access itself, on each workstation. Access includes a database splitter wizard to split the file for you or you can do it manually. If When you move the back end to the server you'll need to refresh the links to it in the front end, which is done with the built in Linked Table Manager. Ken Sheridan Stafford, England > We recently moved an Access database file from a Win98 machine to our main > File Server (Windows 2000 Domain controller). When on the Win98 machine more [quoted text clipped - 5 lines] > change. The db file is saved as Access 2000 and the users are using 2000, > 2002 (XP) and 2003. There is no Access Workgroup security on the file. I tried splitting the db, and got an error 'subscript out of range' and after clicking OK there is no further information. I did a 'compact and repair' and it launched the db when finished, no errors reported. I then tried splitting again, this time I got an error 'subscript out of range' when I click OK, I get 'Invalid procedure call or argument'. When I click OK no further actions occur. Further 'compact and repair's have no effect. Nobody has come accross any errors while using the database. > If you have not already done so you should split the database into front and > back ends, the former containing the forms, reports, queries etc, the latter [quoted text clipped - 18 lines] > > change. The db file is saved as Access 2000 and the users are using 2000, > > 2002 (XP) and 2003. There is no Access Workgroup security on the file. > We recently moved an Access database file from a Win98 machine to our main > File Server (Windows 2000 Domain controller). When on the Win98 machine more [quoted text clipped - 5 lines] > change. The db file is saved as Access 2000 and the users are using 2000, > 2002 (XP) and 2003. There is no Access Workgroup security on the file. What Ken said, and make sure that you're not running over a WAN. Access doesn't like WANs. If you are trying to run over a WAN, search the Access groups for "running Access over a WAN" and start reading. Lots of info there. There are steps you can take to speed your db up but you're probably better off going to SQL Server. Kestrel |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.