>Good to know, those little things are difficult to trace.
>- y luego yo te respondi, chequealo, incluye una invitacion a Fremont! :)
Si, si. Gracias por la invitacion. Algun dia... Alex
>

>>Agustin and David,
>>
>>I found it. Not sure if it was the foxuser or what and don't have a way to confirm anything, as the offender is gone and don't have the energy to try to recreate.
>>
>>Here is what it seems happened:
>>1) The form was maximized in design mode and run.
>>2) WindowState was reset to *default*, which made it OK in design mode, but apparently it still remembered at run time.
>>
>>Correction:
>>3) Set WindowState to 0 - Normal in design mode. Now it runs OK.
>>
>>Thanks for your input.
>>
>>Alex
>>
>>pd. Agustin: Creo que te lo respondi (?)
>>
>>>Alex, sometimes it have to do with a foxuser table going wild, try to find which foxuser.dbf you are using when your form is running, then open it and delete the windows entry. If you are not storing anything important on it deleting it will be the easiest solution.
>>>
>>>
>>>Agustin.
>>>pd. Te envie un mensaje personal hace dias.
>>>
>>>>Hi,
>>>>
>>>>As a form instantiates it suddenly maximizes. I traced Thisform.WindowState and it turns 2 just after the UIEnable event of a a text box, but no code seems to do it. This form is based on Visual Maxframe Professional's frmDEGridNav2Pages and the textbox is txtFind.
>>>>
>>>>Any ideas? TIA
>>>>
>>>>Alex