So what line does it stop on? Or does it actually get to x = 1? What happens next?
Why not just set a breakpoint at the 1st line of Init() and watch what happens in debug (or are you still on VFP3)?
UIt's likely that till Init() is done, the form doesn't "know" its objects, such as Thisform.lblErrorMsg.
>I have a program that executes a login form. If I run the form it works as expected. If I run the form form for the program "DO FORM login" it stops at the init method which has the following code in it
>
>PUBLIC gnuseridcnt , gnpasswordcnt , lcweekday
>LOCAL x
>
>gnuseridcnt = 0
>gnpasswordcnt = 0
>gnUserLev = 0
>m.glValid = .F.
>
>Thisform.lblErrorMsg.Caption = ''
>Thisform.lbltoday.Caption = 'Today is ' + CDOW(DATE()) + ', ' + ;
> CMONTH(DATE()) + ' ' + STR(DAY(DATE()),2) + ', ' + STR(YEAR(DATE()),4)
>Thisform.lblPC.Caption = 'You are using a ' + SYS(17) + ' PC'
>
>IF ! USED('sysuse')
> USE (gcDATA) + '\sysuse' ORDER TAG cid ALIAS sysuse
> SELECT sysuse
>ELSE
> SELECT sysuse
> SET ORDER TO TAG cid
>ENDIF
>
>x = 1
>
>I can add the "DODEFAUL()" command with out any change in behavior. The x = 1 is there so I could have a place to stop in the debugger.
>
>I am stumped. Any help appreciated.
- Whoever said that women are the weaker sex never tried to wrest the bedclothes off one in the middle of the night
- Worry is the interest you pay, in advance, for a loan that you may never need to take out.