Hi Tom,
One thing you could check is that if you have PRGs with the same name as SPRs then VFP will call the SPR directly the second time, bypassing the PRG. I consider this a bug in backward compatibility. This means that often the form will run but your setup code etc will be bypassed and weird stuff can happen.
Eg

*** Main Program ***
Do MyCode        && will do MyCode.prg
Do MyCode        && will do MyCode.spr

**** MyCode.PRG ***
DO MyCode.SPR    && assuming you have a screen of this name

The solution is to explicity put the prg extension in the callDO MyCode.prg or to rename the SPRs

I'll be covering the conversion issues in detail at OzFox in July, so it's a pity you can't make it. Thomas Ganss is on the right track.


>Hi,
> I have been working on a FP2.6 for windows app, transported to VFP6, and have been experiencing strange behaviour when combining "regular VFP6" forms with the "read compatible" generated forms.
> When a read compatible form (eg data entry) calls a "regular" form (a lookup or error screen for example) and returns, it occassionally goes into a strange "read-only" mode.
> All data-bound entry fields become read-only, and the message "record is read-only" appears in the status bar. I cannot fathom a pattern to this (it is reproducable) as some forms work and others don't. The "read-only" state is not detectable/reversable as far as i can tell, except by closing the form...
> Has anyone experienced anything similar to this? Any ideas would be greatly appreciated,
>
> - Tom