Microsoft Access can’t find the database file…” and “The Microsoft Jet database engine cannot open the file…”. Sorry for the lengthiness of this post but I do not know how these problems are related. I think I have reached a "can't see the forest for the trees" point with this problem. I have looked at many posts here on E- E but have not found a solution. I am experiencing two errors, which I think are related. One of the following error messages occurs, depending on the circumstance: “Microsoft Access can’t find the database file FP. Microsoft Office Access File Path Access Error Number 2950Microsoft Office Access File Path Access Error Number 3044Make sure you entered the correct path and file name.”The Microsoft Jet database engine cannot open the file "\\RP4\Access MDBs\FPSD. It is already opened exclusively by another user, or you need permission to view its data. We have a small Win XP Pro workgroup network using simple file sharing. The computers involved with the Access app are named RP1, RP3, RP4, RP5 and T5. One of the computers in the network houses the backend data file of a split Access 2. K database and is also used by one of the users as a frontend client. RP4 was purchased recently and replaced RP3 as the computer that hosts the back end file. The RP4 user is the main user of the Access app. The other users (computers) use the app sporadically with an eye to increased utilization. When trying to open an Access DATABASE (updated to Access 2010 from the original 2007) I have suddenly begun to get the following message" "Microsoft Access can't. 75 Path/File access error. 2036 Application-defined or object-defined error 2037 Microsoft Office Access. Error Numbers and Descriptions for Microsoft Access. ![]()
The database was secured via Access ULS and is opened by the clients using shortcuts that point to a single workgroup file residing on the computer that holds the backend. The Windows File Sharing seems to be set up properly, using the simple file sharing method. ULS was applied to the database years ago and has been functioning without incident since 2. After putting RP4 into service and moving the backend to it, the clients could not link to the frontend. Attempts to link to the frontend throw the following error: The Microsoft Jet database engine cannot open the file "\\RP4\Access MDBs\FPSD. It is already opened exclusively by another user, or you need permission to view its data. After some troubleshooting, I decided to unsecure the database files, following the procedure outlined in an "Accepted Solution" posted by LSMConsulting on 4/8/2. E- E and utilize a new workgroup file just as a login scheme. Now to some specifics as regards the symptoms occurring. I’ll reference RP1 but the other computers exhibit the same problems. RP1 has two Windows user accounts with both being administrators. User. 1 is the owner of the database. This is how the two error messages present themselves after unsecuring the database: User. RP1 is able to open up Access but when he tries to re- link to the back end on RP4, the “Microsoft Jet database engine cannot open the file…” error occurs. When User. 2 on RP1 clicks the shortcut to start up Access, the ““Microsoft Access can’t find the database file FP. Access, referencing the front end as the file that Access can’t open. Windows Explorer (on RP1) will not copy the frontend file from RP4 to RP1, producing the following error: “Cannot copy FPSD. Access is denied.” When I move the backend file to a new, shared folder, the following results: User. RP1 is able to open up Access and re- link to the back end on RP4, without error. When User. 2 on RP1 clicks the shortcut to start up Access, the ““Microsoft Access can’t find the database file FP. Access, referencing the front end as the file that Access can’t open. In troubleshooting these problems, I have used RP3 and RP5 as the “server” (i. BTW, RP5 is also a new computer, identical to RP4, and was put into service the same time. Of course, I will greatly appreciate the input of the experts out there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |