Hi Everyone
We have an office running approx 12 workstations with Access Front-ends linked to an access backend database on a server running Win 2000 Server.
We have a few workstations that have had more problems then others in regard to getting thrown out of the system, etc.. They uniquely have gotten the error shown below:
eRROR #2046
"The command or action '|' isn't available now.@* You may be in a read-only database or an unconverted database from an earlier version of Microsoft Access.
* The type of object the action applies to isn't currently selected or isn't in the active view.@Use only those commands and macro actions that are currently available for this database.@1@@1"
When this error occurs, it usually happens on a save record command button after they have made some edits to a record. It's generally on the same form which is highly used, but not always. Basically, they are unable to edit or update a record at that time, and need to exit the program and sometimes reboot their PC's to get it back up again with edit permissions.
The strange part is that it is very sporatic, and seems to almost move from pc to pc among these three workstations. All other workstations seem fine and don't have nearly the problems these do, although we have gotton alot of Error #0 lately accross the whole office. Every workstation in the office is running Win XP Pro, with 512 ram, with UPS units, etc.. All workstations have updated versions of jet and MS windows SP's. Also, we have thoroughly checked permissions on the server, etc...
Also, our front-end automatically compacts and repairs on exit, and these problem workstations seem to get alot of DB1, DB2, DB3, etc.. databases created. This obviously is due to not having exclusive permission to C&R the front-end. Sometimes, when they exit the program, they see a message saying the front end database has been placed in an exclusive state by their username error msg, and I have seen the front end hold the front-end lock file on these workstations even after they have signed off. The problem is that the settings on their database are definately set to open database in shared mode ?? Finally, these users frequently hang sessions on the server at the end of the day. We also have replaced the NIC cards and verified that they have the same IP network on these PC's just to rule that out.
Any thoughts greatly appreciated !
Thanks
Jackson
We have an office running approx 12 workstations with Access Front-ends linked to an access backend database on a server running Win 2000 Server.
We have a few workstations that have had more problems then others in regard to getting thrown out of the system, etc.. They uniquely have gotten the error shown below:
eRROR #2046
"The command or action '|' isn't available now.@* You may be in a read-only database or an unconverted database from an earlier version of Microsoft Access.
* The type of object the action applies to isn't currently selected or isn't in the active view.@Use only those commands and macro actions that are currently available for this database.@1@@1"
When this error occurs, it usually happens on a save record command button after they have made some edits to a record. It's generally on the same form which is highly used, but not always. Basically, they are unable to edit or update a record at that time, and need to exit the program and sometimes reboot their PC's to get it back up again with edit permissions.
The strange part is that it is very sporatic, and seems to almost move from pc to pc among these three workstations. All other workstations seem fine and don't have nearly the problems these do, although we have gotton alot of Error #0 lately accross the whole office. Every workstation in the office is running Win XP Pro, with 512 ram, with UPS units, etc.. All workstations have updated versions of jet and MS windows SP's. Also, we have thoroughly checked permissions on the server, etc...
Also, our front-end automatically compacts and repairs on exit, and these problem workstations seem to get alot of DB1, DB2, DB3, etc.. databases created. This obviously is due to not having exclusive permission to C&R the front-end. Sometimes, when they exit the program, they see a message saying the front end database has been placed in an exclusive state by their username error msg, and I have seen the front end hold the front-end lock file on these workstations even after they have signed off. The problem is that the settings on their database are definately set to open database in shared mode ?? Finally, these users frequently hang sessions on the server at the end of the day. We also have replaced the NIC cards and verified that they have the same IP network on these PC's just to rule that out.
Any thoughts greatly appreciated !
Thanks
Jackson
