Packaging Wizard Quandary

[Adam Milligan]

All-

I have devloped an Access 2007 app that links to a SQL 2008 backend. I have
packaged the solutuon with the Access Runtime and deployed it to a windows XP
virtual machine. It works fine for me, but when I log in as a test user, I
get a macro error 2950. If I give my test user admin rights on the local
machine, the app works fine. I repackaged the solution to be installed in
"Program Files" "Shared Files" and "App Data" with the same result. How
would I go about packaging a solution that can be installed where anyone can
use it without having to give everyone admin rights to the local machine?
Thanks for any input!

Adam Milligan

 

[a a r o n . k e m p f]

Linked tables are never error-free.

you should move to SQL Server and Access Data Projects-- they simplify
Access/SQL Server tremendously!!

PS - with ADP, you could keep your SQL Server databases-- anywhere you
want-- for example, over the internet--
and then you wouldn't need to give anyone any extra permissions to
store stuff in SQL!

and ADP works over a WAN!
and ADP works over a VPN!

 

[Danny J. Lesandrini]

Adam:

I'm just guessing here, but my first thought was to toggle some Access options
to assure that the distributed app doesn't choke itself with security.

Looking at the Trust Center Settings (Access Options | Trust Center menu), I see
that there's a way to set "Trusted Locations". Have you added your applications
default final resting place to that list? If, for example, you plan for it to be installed to
C:\Program Files\The Shadow Enterprises\

.... then add this path to the trusted locations list.

It's just a thought. And while you're there, you might want to check the Macro Settings
too.

 

[Aaron Kempf knows nothing]

I am never error-free.

you should move me to jail or Iraq-- that would simplify
things tremendously!!

 

[Adam Milligan]

Danny-

Thanks for the input, but it didn't seem to help. After more playing, it
looks like the "least permissive" approach is to just grant all users
read/wirte access to the Shared App Data folder. Not ideal, but it works in
a pinch! Thanks again.

Adam Milligan