'Priveleges' problem with an MDE in Access Runtime

[newToAccessDev]

Hi there,

I have an application that I converted from Access 97 to Access 2003, and from which I've created an MDE file. I want to test the MDE out on an environment that does NOT have Access but instead has the Access Runtime (which is what the users' machines will have). I used Access 2007 Developer Extensions' Package Solution Wizard to create the setup for the application and ran the setup on the test environment, and the application installed ok. My problem is that when I run the application, it opens up, but then after a few seconds a message appears saying: "You do not have the necessary privileges to open this database. Closing Access Program."

I included a workgroup information file (an .mdw file) as one of the files to be installed when the setup is run, and I would think this file should handle privilege/permission issues, so I can't see where things are going wrong.

Does anyone have any suggestions on how to fix this problem? Also, is it necessary to convert the .mdw file to Access 2003? It is currently in Access97 format. Could this be causing the problem?

Any help here would be great!

Thanks,
newToAccessDev

 

[newToAccessDev]

Just to provide an update, but this problem has been solved since I last posted. It was kind of a silly mistake on my part. The message "You do not have the necessary privileges to open this database. Closing Access Program." that was appearing when running the runtime version of my application was coming up because I was providing an incorrect workgroup information file. After providing the correct file path, this message went away.

Another workgroup file problem has also been resolved:
After running the setup and opening the application, I got a message saying something about how Access couldn't find the workgroup file. The problem was that the workgroup file path contained a folder name with a space in it (for instance, "Wrkgrp File"), and Access couldn't seem to process this. So, I went into DOS prompt, ran the command "dir/x" to find the "long" folder name (i.e. the one without a space), and using this folder name in the path (partially) solved the problem. Access still had issues finding the file, seemingly cause the 2007 package wizard had prepended an "/x" before the workgroup specification. After installing the application, going to its properties menu and deleting the "/x" in the target field, the problem went away.

Since resolving this 2nd problem, I've switched to using the 2003 developer extensions, and have not run into any problems having folder names with spaces in the workgroup file path.

Hope this info helps somebody out there!

newToAccessDev