Link to home
Create AccountLog in
Avatar of pcalabria
pcalabriaFlag for United States of America

asked on

Access 2010 Trust Question

Hello,

I'm very new to Access 2010 although I'm familiar with Access 2K.

I've just developed my first Access 2010 applicaiton and provided it to a user who is using the 2010 runtime.
When the user tries to open the applicaiton, they get a blank screen.

I suspect its a trust problem, but being new to 2010 I'm not sure how the user sets up an application to run for the first time.
In order for me to run my own application, I had to go into my software and set up the dirrectory as trusted.
Since the user only has the runtime, we don't know where to go or what to do.

Can you help?

PC
SOLUTION
Avatar of DatabaseMX (Joe Anderson - Former Microsoft Access MVP)
DatabaseMX (Joe Anderson - Former Microsoft Access MVP)
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
ASKER CERTIFIED SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Avatar of pcalabria

ASKER

Thanks for your help.

I'm not sure if I have solved this problem yet, but I did realize several things that I did wrong when I read the related KB article provided by MX.

The article states you should use the Save and Publish option of Access 2010 which I did not know about.  I actually used the save option available when in design mode, and I also did not fix a compile error before sending the user a file, which I suspect is the real problem.

I also noticed that they moved the create accde file to the "Save and Publish" option which probably confused me - who took my cheese! :-)

I'm going to split the points and close this question and then open a new question if the problem still exists.  Since you both (MX and LSM) responded with the same solution within minutes of each other, I'm going to award 166 to each of you for the registry solution which I will save for future use, and 167 for the link to the KB article which helped me figure out what I did wrong!
I'm going to split the points and close this question and then open a new question if the problem still exists.  Since you both (MX and LSM) responded with the same solution within minutes of each other, I'm going to award 166 to each of you for the registry solution which I will save for future use, and 168 for the link to the KB article which helped me figure out what I did wrong!