when these forms are called (all these instances have been from a menu hit), it starts to spit out properties of the form as well as various other output to anywhere it sees fit within the VFP main window. This has happened with 3-4 forms, once with me. Other programmers on this project have run into the same weird behavior, and the only solution was to copy the functionality of the old form to a new one(non-hacked). After this, the form works fine. Shrug, I have yet to figure out the reason for this behavior.


>The structure of scx and vcx files did not change from VFP5 to VFP6. The only difference between a form or library between versions is the compiled code.
>
>What kind of "random" features are you referring to?
>
>>As an aside yet releated to your messages, I have a question. Has anyone had any problems using the "hack" program (x3dthack.prg) with VFP 6.0 forms? I have been working on an application that was started with VFP 5.0 and VMP 3.01, which was then upgraded to VFP 6.0 in September. Ever since the upgrade, any forms that were "hacked" come down with a serious case of "random features". Anyone with the same experience?
>>
>>sc
>>
>>
>>>Visual MaxFrame comes with a hacking tool to make retrofitting apps easier, if still not a joy. This tool opens a selected .vcx or .scx as a grid and guides the changes that need to be made to change class and library names, even making bulk changes (e.g. change all txtbox with mytxtbox). Version 4 is just being released, I think it is worth a look.