Conversion from FoxPro 2.5 (DOS) to VFP 6.0 2

[BytemanJ]

How do I tell my program to use the Courier non-proportional Font? I am trying to convert a very long FP for DOS Program to Visual FoxPro 6.0. I want to keep my original screens the same until I have time to convert them to a non-DOS format. Also, do I need to replace the ASE Library (Dr. Switch) for execution of DOS based commands? Any advice on converting my programs would be most welcome.

 

[Mike Gagnon]

Unfortunately there is no magic wand. Since the DOS screen where "drawn" by code and VFP forms are essentially tables, the concept is totaly different. So a total re-write is in order.

 

[wjs2]

Byteman,

And, unfortunately, mgagnon is correct. What you can do to keep the changes to a minimum for the time being is something like this. You will see portions of this in your 2.6 program where the browse screens are now. Just play with this until you get the look as close as you can, then use that code to replace the browse commands you find in the 2.6 programs. It isn't totally pretty but it gets close to what your after for now. (You may see things here that you are not using so just ignore the extra. Like the menu and toolbars etc.)
____________________________________________
procedure p50_BrowseTheFile
bwcols = scols()
end_row = srows()
define window w_BrowseWindow from 0,0 to end_row,bwcols ;
in screen ;
font 'ms sans serif' , 9 style 'b';
COLOR SCHEME 12 grow ;
title lcVendorID + ' ' + lcVendorName + ;
' <-- SORT SEQUENCE --> ' + lcSortSequence ;
name browsescreen
activate window w_BrowseWindow
select Temp00
go top
Activate menu _apmenu nowait
do Show_ToolBar
browse fields &tmpbrowse ;
font 'ms sans serif' , 9.5 style 'b';
nolgrid ;
norgrid ;
noappend ;
nodelete ;
NOEDIT ;
for ap_prnt >= ' ' ;
rest ;
COLOR SCHEME 12
deactivate window w_BrowseWindow
release window w_BrowseWindow
return

__________________________________________

As for the Dr. Switch library, I'm not familiar with that. However, the easist way to execute other programs is the shellexecute. For my own use, I took a shellexecute example and just made it a small proram to be included in projects.

Good Luck,
WJS

 

[wjs2]

BytemanJ,

Just as an added note.. If you have a lot of '@ say get' stuff in there, this is not going to be pretty. This is why mgagnon is saying a rewrite is in order. My last post would help with pure browse screens and that is about it. Editing, entering information and such is a whole different ball game with Visual Fox. It might even take longer to figure out how to format the screens than it would to just rewrite it.

But, I still wish you Good Luck,
WJS

 

[BytemanJ]

Many thanks to mgagnon and WJS for your understanding responses. I guess I should convert my program to FoxPro for Windows until I find the time to re-write it for VFP. It consists of over 87,000 lines of code in 197 Procedures with thousands and thousands of @ SAY and 1,788 @ GET Commands. It also has over 12,000 lines of Help.

 

[Mike Gagnon]

BytemanJ

Although there are some help out there:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q195514

Micro Endeavor offers a course to help you get through it:

http://www.microendeavors.com/training/ordfrm2.doc

This site promise tips and trick for the conversion process.

There are people out there will to help you (programmer to help you)

http://www.foxdev.com/files/rcb.doc

http://www.erw.com/convert_fox_2_x.html

But BTW not to belittle your dilemma, but 87,000 is not so bad. And &quot;most&quot; of the code is most likely usable. It's mostly the interface. Your procedure should woork without to much changes (execpt maybe date variables)

Hope all this helps