SPLIT Function

  • Thread starter Thread starter Chris C.
  • Start date Start date
C

Chris C.

I'm getting an error "5: invalid procedure call or argument" when executing
the SPLIT function on one of the computers using my application. VB help
recognizes the command and my arguments are sound; I don't have this error
on other workstations. Am I missing some particular file(s) on this
specific workstation?

Chris
 
Check the VBA references on the computer that is failing. Open Visual Basic
Editor, click Tools | References, and see if any are marked as missing.
 
I should have mentioned this before, but I did check for missing references
and all were in place. What do you suggest I do next?

Chris
 
My next "likely culprit" would be if you have a Null value in any of the
delimited values in the text string.

But it also still could be a messed-up reference:

From info posted previously by Douglas Steele:

Your references are probably messed up.

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
 
Back
Top