>Hi George,
>>>
>>>AFAIR I tried doing that with RtlMoveMemory once, but ran into trouble somewhere around 2**31,
>>>which meant for me some problem with the bit defining the sign of the number, or translation problems >>with INTEGER/LONG in the declare line.
>
>>It may be a problem due to the fact that VFP treats all integers as signed. There are several copies of >my string to integer class in the download section.
>
>Ok, I've found your routines and will add them for checking my results - nice and compact due to the parametrization. I also found some similar routines by Ed Rauh, and he documents the usable range of the converted numbers via RtlMoveMemory to the same range. Writing a very small fll-function probably won't get any better speed, because another function call is needed. So back to speeding up vfp code.
>
>thanks,
>
thomas,

Thanks for the kind words. When I wrote the routines my object was explicitly to overload the functions while keeping the utility at its highest.

Ed's solutions, while, as usual, were exact and correct, this was one of the few things we disagreed on (in terms of design). I still miss him greatly.

I'll agree that you probably won't (but might) get better performance with an FLL. My feelings about doing something like that is, "Is the view worth the climb?" Plus, it's just one more thing you have to maintain.

Regards,