Convert .adp to .ade from 2002 to 2003 and deployed

[Stephanie Neveu]

Hi all!

I have 4 2002 .adp that I recently upgraded to 2003 and then made .ade to
deploy. (Before I deployed 2002 .adp). Well, now that my users have the
new application on their computers things that I haven't changed no longer
work for them but they used to before I deployed the 2003 .ade. Does anyone
have any help on this? I called Microsoft and they haven't been much help.
It seems to be a problem somewhere in the deployement because the developing
maching cannot reproduce their problems.

Also, now that my users are using 2003 .ade they continue to get a
"security" warning box whenever they open the application. How do I get rid
of that. I already changed the developing machines security to low.

Any help on this would be great! Thanks in advance.

Stephanie

 

[Sylvain Lafontaine]

Have you tested the 2003 ADP file directly on the user machines to see if
the error if with the Access 2003 or with the ADE version?

Check the references for any missing component or a swapping int the order
of the libraries.

For the security warning, this setting must be set to low on each user
machine; as this is not a setting that got transfered with the ADP or the
ADE file.

S. L.

 

[Stephanie N]

i haven't tried that specifically but i did try the following:

On the developers machine everything works fine in the .ade.
I can connect to the users machine and open the .ade and everything works
fine
I can even log on as one of the users to the developing machine and it works
fine.
But if I go to the users computer and try to log on the same problem that
they have, I expierence.

When I called Microsoft they had me create new projects and import
everything in to the new project then redo all my references. These new
projects are the ones that are having the problem.

With this info - would you still suggest testing with an .adp? I was trying
to get away from the .adp on the users machines.

 

[Stephanie N]

Also, how do I change the security level of the users machines when all they
have is access runtime on it.

 

[Sylvain Lafontaine]

Then maybe your problem is coming from the Access runtime. For example,
it's quite possible that the latest service pack has not been installed on
their machines. You should really try with the ADP file.

For the security setting, I don't know. Sagekey (www.sagekey.com) have
probably a script for this but they are not free. You can also use
Authenticode on your ADE file.

With only 4 user posts, you should try replacing the runtime with a full
Access deployment and stop losing time with this.

S. L.