>>Should I debug the code?
>
>If you like. Update the code with any fixes you may need to do and email me a final copy. I will update the download version with credit to you for the debugging. I do not recall who actually wrote the code. It was given to me over ten years ago.
Ten years ago? Wow. First I tried the function in ctl32, but it is too heavy weight, consuming too much bytes and bearing the risk of bugs due to the overhead. Your function is surprisingly light weight and does (should do) all I want. :)
I'l try to find the causes and will keep you informed.
UPDATE:
Debugging the code revealed that tthe parameters that I mentioned are totally ignored in the code! That explains it all. :-)
But I also discovered that I built an app in 2008, based on the VFPX code of the FFC classes. So, I'll not gonna improve your stuff. Instead, I'll gonna use my 2008 app.
The VFPX project can be found here:
http://vfpx.codeplex.com/releases/view/10925Thanks
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
