By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,247 Members | 1,989 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,247 IT Pros & Developers. It's quick & easy.

MDE doesn't work on target machine -- Access 2000

P: n/a
I have Access 2000 installed on a machine and I create the MDE just fine.
When I copy the MDE file over to another machine that has Access 2000
installed, the references are hosed and I get unable to find function error.
There are no third party controls in the application.

This target machine is on a network requiring domain login, but the user is
set up as a Local Administrator.
Any ideas or code that I can use to work arount this problem? The only work
around I have found is to copy the source code to the target machine and
make the MDE there.
Thanks!

Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Here's a good reference (no pun intended):
http://members.rogers.com/douglas.j....nceErrors.html

--
Shane Suebsahakarn
----
Head of IT
PAN Telecom
Tel: +44 (0) 870 757 7001

"Barry Young" <yo******@insightbb.com> wrote in message
news:p5dXc.62873$Fg5.49786@attbi_s53...
I have Access 2000 installed on a machine and I create the MDE just fine.
When I copy the MDE file over to another machine that has Access 2000
installed, the references are hosed and I get unable to find function error. There are no third party controls in the application.

This target machine is on a network requiring domain login, but the user is set up as a Local Administrator.
Any ideas or code that I can use to work arount this problem? The only work around I have found is to copy the source code to the target machine and
make the MDE there.
Thanks!


Nov 13 '05 #2

P: n/a
Hi Shane,

The strange thing about this particular situation is once I copy and create
the MDE on the target machine, everything works without changing or setting
any references. The target machine is part of a domain.

I make the MDE on the target machine without changing any references, and
again it works fine. I just can't copy the .MDE file from my laptop to the
target machine and have it run with out the function error.

Any ideas?

Thanks!

Barry
"Shane Suebsahakarn" <sh***@REMOVETHISgcicom.net> wrote in message
news:cg**********@hercules.btinternet.com...
Here's a good reference (no pun intended):
http://members.rogers.com/douglas.j....nceErrors.html

--
Shane Suebsahakarn
----
Head of IT
PAN Telecom
Tel: +44 (0) 870 757 7001

"Barry Young" <yo******@insightbb.com> wrote in message
news:p5dXc.62873$Fg5.49786@attbi_s53...
I have Access 2000 installed on a machine and I create the MDE just fine. When I copy the MDE file over to another machine that has Access 2000
installed, the references are hosed and I get unable to find function

error.
There are no third party controls in the application.

This target machine is on a network requiring domain login, but the user

is
set up as a Local Administrator.
Any ideas or code that I can use to work arount this problem? The only

work
around I have found is to copy the source code to the target machine and
make the MDE there.
Thanks!



Nov 13 '05 #3

P: n/a
Hi, Barry.
The strange thing about this particular situation is once I copy and create the MDE on the target machine, everything works
Strange? No. The "failing" MDE file was created on a computer configured
differently than the target computer, so Access is trying to resolve the
References for the application, but it fails in at least one instance. The
"failing" MDE file was successful only when using its native configuration.
Your "successful" MDE is successful in its native configuration, too. When
you move this "successful" MDE from the target computer to the development
computer, you'll likely find that it fails on that foreign configuration,
too.

Check the References in the MDB on the development computer. Is your
application using any libraries other than the default libraries? Access
can often resolve the default libraries if these libraries are located in a
directory on the target computer different than the directory on the
development computer. However, non-default libraries located in directories
on one computer that aren't located in the exact same location on another
computer will often cause the missing References issue, even if the file is
located *somewhere* on that target computer and the file version is the
same. With an MDB or MDA file, one just recompiles the source code to allow
Access to change the paths for the required libraries. With an MDE, no
changes to References can be made.

The default libraries for Access 2K are:

Visual Basic for Applications
Microsoft Access 9.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library

The References dialog window will show the exact locations of these
libraries and any other libraries your application uses on the development
computer. If you take the same steps on the target computer, you'll find
that some or all of the file locations don't match.

So, you can take Shane's good advice to follow the recommendations of other
Access experts who have been down this same road before, or continue to use
your work-around of compiling the database on the target computer, or change
the configuration (uninstall, then reinstall Microsoft Office) of either the
development computer or the target computer so that the configurations match
(i.e., all file paths are the same) to avoid the missing References issue.

You'll have to decide which method offers your I.T. environment the most
productive, cheapest, or least time-consuming means to solve this common
problem.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Any human can read my reply E-mail address and should alter it so that a
message will be forwarded to me. Spammers are free to use my UNALTERED
reply E-mail address. I will *never* get those messages!)
"Barry Young" <yo******@insightbb.com> wrote in message
news:viwXc.240205$eM2.35580@attbi_s51... Hi Shane,

The strange thing about this particular situation is once I copy and create the MDE on the target machine, everything works without changing or setting any references. The target machine is part of a domain.

I make the MDE on the target machine without changing any references, and
again it works fine. I just can't copy the .MDE file from my laptop to the target machine and have it run with out the function error.

Any ideas?

Thanks!

Barry
"Shane Suebsahakarn" <sh***@REMOVETHISgcicom.net> wrote in message
news:cg**********@hercules.btinternet.com...
Here's a good reference (no pun intended):
http://members.rogers.com/douglas.j....nceErrors.html

--
Shane Suebsahakarn
----
Head of IT
PAN Telecom
Tel: +44 (0) 870 757 7001

"Barry Young" <yo******@insightbb.com> wrote in message
news:p5dXc.62873$Fg5.49786@attbi_s53...
I have Access 2000 installed on a machine and I create the MDE just fine. When I copy the MDE file over to another machine that has Access 2000
installed, the references are hosed and I get unable to find function

error.
There are no third party controls in the application.

This target machine is on a network requiring domain login, but the user
is
set up as a Local Administrator.
Any ideas or code that I can use to work arount this problem? The
only work
around I have found is to copy the source code to the target machine

and make the MDE there.
Thanks!




Nov 13 '05 #4

P: n/a
I found the culprit. There were three references in that didn't need to
be checked (utility OLE Automation etc).

Removed the references but I still need to test it on the target
machine.

If I have a problem, I'll post more to this thread.

Thanks again for your help.

Barry


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.