I have created an Access 2007 database that will be used by about 200 users. The front end will reside on the users desktop and the back end will be on a network folder. I used the database splitter to split the database and put the backend on the network drive. I email the frontend to a few users to test and some of them had access issues. Users recieved error code 3044 stating that the path is not valid. I think it has something to do with Trust Center. Can anybody suggest what might be happening. It works for me but I have trust center Macro Setting set to Enable all macros. Any help would be appreciated.
-
-
I would check first that the error message isn't the simple explanation. We can't tell you as you don't even include it in the question.
Whatever it indicates is not valid, check out. Worry about less obvious possibilities when the obvious ones have been eliminated. -
Not sure what you mean. The simple answer would be that the path to my backend database is incorrect but I used the database splitter utility and the path is correct. The error being throw back is the following
3044:S..... is not a valid path. Make sure that the path name is spelled correctly.
The app works for me but not for some of my users.Comment
-
Do they have their networks drives mapped to the same letters as you do?
I worked once for a client where every user manually had to map their network drives, and assign letters for em......That was a mess.Comment
-
Unfortunatlly the drives are mapped to the same letter but I'll look out for that in the future.Comment
-
Does it work for some users(besides yourself)?
If your at the failing users computer, and navigate via explorer, can you "find" the backend database?
Do you have any code in your DB where you use path information?Comment
-
It does work for another guy and I fooled around with his trust center setting so he wouldn't get the secuity warnings for a different project. That's why I'm leaning toward Trust Center being the problem. the only path info is for the linked tables and I can find the back end db on the failing pc's. The error they receive is 3044-invalid path.Comment
-
Im out of ideas. Hope you find a solution and when you do, please remember to post it here :)Comment
-
That is exactly what I mean.
It's harder to help without the actual path but you seem to feel this may be private information (I assume). That is the interesting part of the message of course. I could have checked that for some errors, or issues, but I'll leave that to you.
What I would suggest from here is that you go to a user's PC that is failing and simply do a rename of "whatever is the file that is referred to in the message" to itself. If you have adequate rights to that file then the command will succeed. If it fails then your problem is nothing to do with Access (which isn't a bad thing necessarily). You will need to arrange for the file to be made available somewhere where the users have full access to it. If it succeeds then it would indicate that there is indeed something within Access which is struggling to work in the environment as you have it set up. I'm afraid Access 2007 was not the easiest version to use in situations like this. In my circles it is not well thought of at all.
On the up side - 2010 is considered something worth moving to.Comment
-
Be sure that the users have write access to the network drive.
Access will fail when there's no possibility to create the .ldb file or adding a new user to it.
Nic;o)Comment
Comment