>>>Just upgraded apps to VFP6 and running into a problem
>>>running wordnum function in foxtools. We use this function all over
>>>the place with 2.6 and 5.0 but now with 6.0 it's giving us some problems.
>>>Not every hit on wordnum() gives error but it is happening pretty frequently.
>>>Anyone seen this?
>>>
>>>Giving Error number: 2028
>>>Message text: API call caused an exception.Program: myprogram
>>>
>>>
>>>thanks,
>>Ronnie,
>>
>>I've seen this in one instance with other Foxtools calls, but limited to one particular machine. While I haven't been able to resolve it yet, if I were to start looking at a possible cause, I'd look at the MSVCRT.DLL. I first find a machine were everything worked fine, then look at the version number of this DLL and compare it against the version on the machine that didn't have this problem. Chances are that the problem machine has an earlier version.
>
>Thanks, George. I have this problem lots of times with this piece of code:
>

lcLibrary=SET('LIBRARY')
>SET LIBRARY TO sys(2004)+"foxtools.fll" ADDITIVE
>GetWind=RegFn("FindWindow","CC","I")
>wclass=0
>winName=Left(_screen.caption,len(_screen.caption)-1)  && Trim off the colon  - findwindow did not like that.
>apphand=CallFn(GetWind,wclass,winName)

>
>We have Windows 95 here and this problem occurs about 2 times from each 10 runs.

Mine occur with _Whtohwnd(_WFindTitl(ThisForm.Caption)) and, as I said, only on one machine which probably is a Win95B box.

BTW, if you simply want the window handle of the main VFP screen, try Mainhwnd(). Of course, in VFP 7.0, you don't need any of this.< g >