Access 2002 Runtime - networking errors

S

Sapper

I manage an Access 2002 runtime database remotely, with back end mounted on a
Windows 98 server, and front ends (mde) working on a variety of Windos 98 and
XP workstations. The network uses Windows 98. My database has worked
extremely well and robustly until last week when I made some changes to the
front end. To accommodate these modifications, I also changed some data
types in the tables, and added some new fields.

After I modified the front end, I opened a new database, imported all
objects, compiled an mde version and copied this back to the workstation to
which I have remote access (Citrix) . The users then copied this front end
from there, to the other workstations. I also copied the backend tables on
to the server.

We have done this several times in the past. But now, only the version I
copied to them works correctly. The other front ends open, but on initiating
any event with code behind a command button, for example, I get error
messages telling me that the event isn't defined or that it can't be
evaluated.

When the same code is initiated using the first copied version, there is no
problem and the database responds as expected - and it is seemingly fully
functional.

In the recent modification, I did not change the code behind the command
buttons now leading to these errors - so it would not seem to be linked in
this way. Besides, why would the code run smoothly on one machine, but on no
others, when the front ends are perfect copies?

I would have been moderately happier, if none of the front ends worked, and
am baffled than one does but the others which are mounted on a mix of XP and
98 machines don't - so the OS wouldn't appear to be the culprit.

I have also asked them to run the database exclusively from each
workstation, with other front ends closed, but the same errors occur.

Please help, and point me in the right direction to help solve this.
 
S

Sapper

I assume you mean the References in the code modules within Access. If so,
yes, as the database is compiled into an "mde" database here and then copied
to each workstation. All workstatons have exactly the same version of the
front end, that's what's so confusing.
 
D

Douglas J. Steele

Just because the application could be compiled into an MDE and that MDE
distributed to all workstations does not means that there isn't a problem
with the References. What causes References problems is one (or more) of the
references being a different version on the target machine then on the
development machine (or the reference being in a different location, or the
reference not existing...)

I've outlined one approach to resolving References problems with MDEs at
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html

In a nutshell, you need to determine the location of each reference and its
version on the development machine, then ensure that the same version of
those files exist in the same location on the target machines.
 
G

Gina Whipp

Yes Snapper that is exactly what I meant

Thank you Douglas for explaining it so eloquently! AND providing a link for
him to fix it!
 
S

Sapper

Dear Douglas and Gina

Thank you both for your help, and for pointing me a definite solution
Douglas. Onbviously, I have much to learn yet....

If I can't work it out, I'll call for more advice if I may.

Many thanks

Simon
 
Top