Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Length of Function name causes bug
Message
From
20/06/2003 15:39:40
Dave Macfarlane
Condo Navigator Ltd.
Alberta, Canada
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Length of Function name causes bug
Miscellaneous
Thread ID:
00802404
Message ID:
00802404
Views:
38
F.Y.I.

I've just solved a problem that has occurred only when running EXE.

A procedure includes three calls to a UDF in the same FOR/ENDFOR loop, ie;

lcValue = GetMySubStr(cString,'Search For','Stop At')
lcValue = GetMySubStr(cString,'Search Next','Stop At')
lcValue = GetMySubStr(cString,'Search Again','Stop At')

The above code works great in development but not in EXE. When running EXE the third attempt at GetMySubStr() doesn't even call the function.

I copied GetMySubStr.prg to GetTest.prg and then changed the third UDF call to GetTest() and it then works in the EXE.

I then renamed all the calls from GetMySubStr() to GetTest() and again it works.

Finally, I renamed Function: GetMySubStr() to GetMySub() and it too works.

I have to assume there is a problem calling the function when the length of it's name is longer than 8 characters.

I'm using VFP 6.0 SP5 on Win 2000.
Next
Reply
Map
View

Click here to load this message in the networking platform