If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Problem with new database
All,
Access 2003, Win XP, some sort of huge server. I re-wrote (for the fifth of sixth time) the database we use for tracking employees, work locations, and various bits of information. The newest database still has about a dozen tables, but a simpler relational structure. Anyway, everything was working on my machine and my boss pressured me to move the new database into production. So, I corrected what I could, split the database, put the backend on the server and emailed the front end to the various users. As you might expect, it doesn't always work right on other desktops. (everyone still has XP and office 2003) Users get messages such as "table locked by another user" and "can't locate macro". The fields may or may not allow for searches and filters. A calculation on one form will only calculate on my desktop. What are some things to check for? (or uncheck?) Thanks! |
#2
|
|||
|
|||
Problem with new database
1. All users of the database must have at least read, write, create, delete
(or modify) privileges to the folder holding the backend database file. Not just the database .mdb file, but the entire folder. 2. Open the database and go to Tools, Options, and Advanced Tab. Set the Default Open mode to Shared and the Default Record Locking to Edited Record. (While you are in the Options area, go over to the General tab and turn off Compact on Close and Name AutoCorrect. Trust me on this.) 3. It’s possible that someone has manually opened the database exclusively. In that case go to the folder holding the .mdb file and open up the same named .ldb file in Notepad. You might be able to read which users are in the database and locked it. Apply 2”x4” as necessary to user. However that should give a "file already in use" error. To stop this from happening create a shortcut for each user on their desktop or off the Start button. It should list the target as the database file and look something like: "P:\Databases\Database File.mdb" 4. It's possible that the users don't have the same drive mappings. Your P-drive could be their M-drive. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Rotata" wrote: All, Access 2003, Win XP, some sort of huge server. I re-wrote (for the fifth of sixth time) the database we use for tracking employees, work locations, and various bits of information. The newest database still has about a dozen tables, but a simpler relational structure. Anyway, everything was working on my machine and my boss pressured me to move the new database into production. So, I corrected what I could, split the database, put the backend on the server and emailed the front end to the various users. As you might expect, it doesn't always work right on other desktops. (everyone still has XP and office 2003) Users get messages such as "table locked by another user" and "can't locate macro". The fields may or may not allow for searches and filters. A calculation on one form will only calculate on my desktop. What are some things to check for? (or uncheck?) Thanks! |
#3
|
|||
|
|||
Problem with new database
Jerry,
Thank you for your insight. After reviewing the suggested settings, the problem appears to be with folder security. Looks like a job for *ITS*. Rotata -- "Jerry Whittle" wrote: 1. All users of the database must have at least read, write, create, delete (or modify) privileges to the folder holding the backend database file. Not just the database .mdb file, but the entire folder. 2. Open the database and go to Tools, Options, and Advanced Tab. Set the Default Open mode to Shared and the Default Record Locking to Edited Record. (While you are in the Options area, go over to the General tab and turn off Compact on Close and Name AutoCorrect. Trust me on this.) 3. It’s possible that someone has manually opened the database exclusively. In that case go to the folder holding the .mdb file and open up the same named .ldb file in Notepad. You might be able to read which users are in the database and locked it. Apply 2”x4” as necessary to user. However that should give a "file already in use" error. To stop this from happening create a shortcut for each user on their desktop or off the Start button. It should list the target as the database file and look something like: "P:\Databases\Database File.mdb" 4. It's possible that the users don't have the same drive mappings. Your P-drive could be their M-drive. -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Rotata" wrote: All, Access 2003, Win XP, some sort of huge server. I re-wrote (for the fifth of sixth time) the database we use for tracking employees, work locations, and various bits of information. The newest database still has about a dozen tables, but a simpler relational structure. Anyway, everything was working on my machine and my boss pressured me to move the new database into production. So, I corrected what I could, split the database, put the backend on the server and emailed the front end to the various users. As you might expect, it doesn't always work right on other desktops. (everyone still has XP and office 2003) Users get messages such as "table locked by another user" and "can't locate macro". The fields may or may not allow for searches and filters. A calculation on one form will only calculate on my desktop. What are some things to check for? (or uncheck?) Thanks! |
Thread Tools | |
Display Modes | |
|
|