Broken Reference

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

This has happened a couple of times and I'm not to sure why and how to fix
it. I send out a new install of my program. I use the developer package to
package up the program for the install. I have one client that install the
program on her desktop and everything works just fine. When she installed
the program on her new laptop everything looks like it installed fine and
runs like it should, the only problem is when she runs a report instead of
the date showing up it comes up with a name? in the field for the date, in
the report the field has =Date() in it. Does anybody have an answer as to
why it will work on her desktop but not on her laptop? Also what can I do to
fix the problem.
Thanks for any help.
 
One of two possibilities
The DLL the date function is in is not installed on her lap top.
(Sorry, I don't remember which one it is)
Or
There is a difference in versions between the two machines. A different
version will often mean a different DLL name.

Since you are not distributing full Access, you will need to check the
Library References to see what files are being used and where they are
located, and check the laptop to see if the files exist and are where the
reference expects them.

If that fails, I have found that 2 rounds of #7 shot from a side by side
will eliminate any problem with a lap top. (Just be sure the user doesn't
still have it in her lap)
 
Back
Top