Converting FoxPro 2.0 to Visual FoxPro 6.0

[michel392]

Hi,
I've been happy developing application in FoxPro 2.0 for the last 10 years. I've acquired the Visual Studio 6.0, in order to use the Visual FoxPro 6.0.
I took an application developed in FoxPro 2.0 and opened it as a new VFP project. The application seems to work well inside the developing VFP environment (by executing .PRG's files through the command window). But after compiling the application, the executable file doesn't work like it worked in the development VFP environment. The characters in the screen change (ex.: instead of a graphical character, it shows a "!" character. I've been tried for a month to solve this problem).
Could someone in this community help me please ? Can you indicate documents thar say about migrating from FoxPro 2.x ?
Thank you very much
Michel

 

[jschenke]

Hi Michel,

I too have the Visual Studio 6.0 and once things return to a normal pace here at work, i'm planning on doing some experiments with Visual FoxPro 6.0

At this point, my best guess is that the fields have a format that contains a '!' and that this format is not supported in Visual FoxPro runtime.
If I'm not mistaking, the '!' means the field has to be the exact width of the variable as initialised when you enter the field.
Check the help file for the supported 'pictures' is what i believe they call it -- there might have been changes in comparison to these supported by FoxPro 2.x

Best regards,

Jan Schenkel.

"As we grow older, we grow both wiser and more foolish at the same time." (De Rochefoucald)

 

[infinitelo]

switching from fox for dos to a visual enviornment can be frustrating, one key point to remember is that you will lose a lot of control over how the program will appear, and how the user will interact with your program. the "guts" of the program will not change much, anything you will present to the user needs to be in the format of what they call "forms" they are really wierd when you first make them, but after you get used to using them you wonder how you managed to use @say's