Split() function returns Invalid procedure call or argument

[GPO]

Can anybody say why the split() function in MS Access 2000 is so
temperamental?

There have been several posts on Google about the "invalid Procedure call or
argument" error it periodically generates, but none really clarify:
* whether it is a recognised "issue" (bug), or
* why it occurs, or
* why including certain values the last (optional!!) argument seems to
solve the problem.

Given the flavour of the some of the NG posts and the fact that one day it
works fine, and the next day on a different PC it doesn't, I'm not going to
bother posting code. I know it's right. I'm just wondering if anyone can
clear up what is going on.

Regards

GPO

 

[Van T. Dinh]

See MichKa's Web site:

http://www.trigeminal.com/usenet/usenet001.asp?1033