Access 97 Macro not running from XP

  • Thread starter Thread starter proctorkidwell
  • Start date Start date
P

proctorkidwell

A command-line command "C:\PROGRAM FILES\MICROSOFT
OFFICE\OFFICE\MSACCESS.EXE" C:\SQLCDD\ALL_LNKS.mdb /X
TheBuild.GenerateSnapshot_4WIN95 /CMD FD*" that has been
running until we upgraded both to a new machine and
converted the tables to SQL Server from Access 97.

At this point we get the error "The Function you entered
can't be used in this expression. *You may have used a
DoEvents, LBound, UBound, Spc, or Tab function in an
expression. *You may have used an SQL aggregate function,
such as Count, in a design grid or in a calculated control
or field.

I have run functions that don't require parameters and
they work fine but when a parameter is added I get the
error. Also, I removed the Command$ from the function call
within the macro "=AutoSetProjectList(Command$())" and the
error is not generated but that I presume is still the
parameter... Does anyone have a clue what I can do with
this to get it to run???

Thanks in advance.
 
Office XP is installed into
PROGRAM FILES\MICROSOFT OFFICE\OFFICE10\
directory by default. Note the 10 after Office in the subfolder name.
 
Sounds to me as though you may have a References problem.

This 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, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). 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)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html
 
[email protected] said:
A command-line command "C:\PROGRAM FILES\MICROSOFT
OFFICE\OFFICE\MSACCESS.EXE" C:\SQLCDD\ALL_LNKS.mdb /X
TheBuild.GenerateSnapshot_4WIN95 /CMD FD*" that has been
running until we upgraded both to a new machine and
converted the tables to SQL Server from Access 97.

At this point we get the error "The Function you entered
can't be used in this expression. *You may have used a
DoEvents, LBound, UBound, Spc, or Tab function in an
expression. *You may have used an SQL aggregate function,
such as Count, in a design grid or in a calculated control
or field.

I have run functions that don't require parameters and
they work fine but when a parameter is added I get the
error. Also, I removed the Command$ from the function call
within the macro "=AutoSetProjectList(Command$())" and the
error is not generated but that I presume is still the
parameter... Does anyone have a clue what I can do with
this to get it to run???

Thanks in advance.
Click to expand...
 
Back
Top