>Hi Edward,
>
>I just wanted to let you know that I've been getting alot done.(Alot at my speed, probably a little at your speed). Anyhow, I had a problem that I did a work around to correct, but I wanted to ask you what you think could cause it.
>The problem:
>In a findcust form I get oApp.topform.custid set,then go to the invoice form and use a fillcust method to setup the textbox values of the cust info. When I run a new form referencing that same oApp.topform.custid property, the value is reset to 0. I searched all areas of the code with the Find box and I'm positive I didn't refer to oApp.topform.custid anywhere. So I have no idea how the custid changed to 0. I checked the value in many parts of the program (using =messagebox(str(oApp.topform.custid)) in various parts of the program)to diagnose the point where the value changes. I've isolated the change to the point when the fillcust method ends (value still is correct) and then I setfocus to textbox for inventory entry(value still is correct) and when I click a command button that calls the =messagebox(str(oApp.topform.custid)) the value is 0. No procedures, other than the button click, are run in the time between the value is correct and the value is 0. The command button is the point
>of change. Could there be a bug in VFP6.0? Or is there something I missed? My workaround is to re-set the value of custid again (oApp.topform.custid=thisform.txtCustid.value). From that point on the program works ok.
>I'll keep working on the rest of the program and keep you posted.
>Otherwise, I hope you had a good vacation and all is well with you.
>
>Thanks
>Best regards,
>Allen

Private message has been sent. Thank you.