MS Access97 - Function Names Not Being Recognized

[Joe Rigley]

Please Help,

I have an MS Access 97 DB that was developed by someone who no longer works
at my company. Many, if not all, of the standard VBA functions like Left(),
Mid(), IsNull() and such in the code behind page of the Form are not being
recognized.

Inorder for the form to run, I have to prefix these functions with "VBA.".
Therefore, they look like this:

Dim strTmp as String
strTmp = VBA.Left(strName,8)

or

If Not VBA.IsNull(txtMRN) then
....
end if

Can anybody tell me WHY this is happening and how I can resolve this
issue??? I checked the References in the code behind page of the form and
"Visual Basic for Applications" is checked.

I am running the DB on Win2003 Svr Standard edition. The db was developed
using the Access 97 Developer's Tool Kit (if that makes any difference).

Any and all comments are welcomed.

Thanks,
-Joe

 

[Douglas J. Steele]

You say that "Visual Basic for Applications" is checked in the References
dialog. Are any of the other checked ones marked as "MISSING:"?

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)

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.

 

[Joe Rigley]

Doug,

Fantastic Information... Even ythough the VBA reference was good, there was
a missing reference to another .ocx object. As soon as I repaired that
reference, all is well.

I don't know how I would have figured that out without your assistance...
Start the weekend early man... You've earned it! YOU ROCK!

Much appreciated,
-Joe

 

[kakha Sikharulidze]

Doug,

Fantastic Information... Even ythough the VBA reference was good, there was
a missing reference to another .ocx object. As soon as I repaired that
reference, all is well.

I don't know how I would have figured that out without your assistance...
Start the weekend early man... You've earned it! YOU ROCK!

Much appreciated,
-Joe