ADP works, ADE on same machine does not

[Guest]

I installed Access 2003 runtime on a Windows 2000 system and tried to start
an ADE which I had prepared shortly before on the server where the SQL Server
2000 database resides. I had to do so because the connection had to be
changed because we transferred the adp from the development environment to
the production environment. The ADE returns errors like 'The expression you
entered as OnClick Event...' and problems with 'str, left, right, asc'.
However I can start the adp, which was the source for creating the ade, on
the same machine without any problems. Since there is no office installed I
cannot really debug...
Any ideas where to start thinking?
TIA,
Norbert Meiss

 

[Philipp Stiefel]

I installed Access 2003 runtime on a Windows 2000 system and tried to start
an ADE which I had prepared shortly before on the server where the SQL Server
2000 database resides. I had to do so because the connection had to be
changed because we transferred the adp from the development environment to
the production environment. The ADE returns errors like 'The expression you
entered as OnClick Event...' and problems with 'str, left, right, asc'.
However I can start the adp, which was the source for creating the ade, on
the same machine without any problems. Since there is no office installed I
cannot really debug...
Any ideas where to start thinking?

Check your refrences (Menu "Tools"->"References" in the VBA-Editor) of
the ADP you used to create the ADE. Remove all refenrences that you do
not need, make sure any refenrence you need is available on the target
machine.

HTH
Phil

 

[Guest]

Thanks Phil,

but the ADP uses the same references on the same machine and works! I did
see some differences in the versions of some references (compared to the
development environment) but since the ADP doesn't have problems, I have no
more ideas.

Regards, Norbert

 

[Norman Yuan]

I'd guess your ADE file was not generated on this problemic machine, was it?

 

[Guest]

Yes, you are right. It was generated on the server with the SQL Server 2000
database, since the problem machine - the client system - even doesn't have
Access installed.
Then the ADE was copied to the client system where we previously installed
the Access runtime and it didn't work. To investigate the problem we then
copied the ADP to the client and opened it with Access Runtime and it worked
properly.

 

[Norman Yuan]

So, you may try to re-create the ADE on the machine where the Access
Development Extension installed and then package the Access runtime and ADE
for deploying to computer without Access installed. (I never used Access
runtime for my Access app, though).

 

[Philipp Stiefel]

but the ADP uses the same references on the same machine and works!

Yes, I quite got that.

I did
see some differences in the versions of some references (compared to the
development environment) but since the ADP doesn't have problems, I have no
more ideas.

Unfortunately problems with the references can not always be
explained with simple logic. I highly recommend that you still
do what I wrote in my last posting, even if it seems to haven't
much sense as the ADP works.

I may be quite possible that Access is able to correct problems
with references in an ADP while it can't do that in an ADE.

Cheers
Phil