Data()

[Anthony Ching]

I have a problem when I wrote the following in a Macro:
SetTempVar CurrentDate, Date()
When I run the program on the development PC, I don't have a problem.
However, when I deploy the database using Access Runtime, on another computer
it now tells me that "it has a function name that the database can't find"
with error 2950.

Can someone please help. Thanks.

 

[Douglas J. Steele]

Your References collection is probably messed up.

References problems can be caused by differences in either the location or
file version of certain files between the machine where the application was
developed, and where it's being run (or the file missing completely from the
target machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window). Select Tools | References from the menu bar. Examine all of
the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

 

[Anthony Ching]

The machine I tried on does not contain Access 2007 or Office 2007. It is
just the Runtime version I tried.

 

[Douglas J. Steele]

Doesn't matter. In actual fact, the runtime is the same executable as the
regular version, with many features disabled through literally hundreds of
registry entries.

Unfortunately, though, having only the runtime does make it a little more
difficult to debug, since you can't get to the References collection.

What you need to do is, on the development machine, identify all of the
references, exactly where they're located on the machine and what version
each is. Once you've done that, you need to ensure that the exact same
version of each of the referenced files exists in the exact same location on
each of the client machines.

 

[Anthony Ching]

I have solved the problem by packaging the drivers in the runtime. Thanks.