Hi Mike

I have to disagree (my opinion). It may be intentional but it's a pain and I

would call it either a bug or bad programming. For example CSV may not

always have anything between the commas. And you may not always have control

of what is sent. In this instance I got over it but I wonder how many other

places I have used GetWordNum and not even known it had failed. Before it

appeared in VFP I wrote my own, I wish I stuck with that now. At least that

worked.

Al

-----Original Message-----

Personal opinion ahead...

Not sure I'd call that a bug...technically you are asking it to deal with

null, not blanks. If you put a space between the commas instead of nothing,

it works as you expect. Check out GetWordCount()...which acts the same

way...it 'ignores' the non-existant "thing" between the 3rd and 4th commas,

and the 4th and 5th commas.

I suspect this was more of an intentional, but undocumented (at least in the

Fox Help) "feature" that had to be handled one way or the other.

(either ignore "nothing" or count it.)

But, it would have been nice had they offered a switch to include, or not,

and had documented this behavior.

So, while I wouldn't call it a bug in VFP, I would call it an undocumented

feature...which often masquerades as a "BUG!"

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/001d01cf5683$4ad19f30$e074dd90$@com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.