>Sorin,
>
>I haven't used the transporter since VFP3, and it wouldn't have much of a reason to exist after that version. VFP3 is the last version that supported Macintosh, so that's why it was the last version where it was of any real use. I suppose it has been getting included in later versions of VFP just because if they didn't do that people would ask where it went. :-)
>
>The transporter is actually used to move code from Windows to Mac and so forth from within the same version of FoxPro. It has been around since the older versions of FPW/FPM/FPD/FPU.
>
>The converter is what took code from FPW to VFP.

While the converter is really bad for converting screens to forms (it leaves them in Read Emulation Mode and they behave so DOSish... ugly), it's still indispensable for reports and labels. I'd much rather recommend download #9450 by our very own Alejandro Sosa - it'll give you screens converted into real VFP forms.

The VFP Converter/Transporter is also a great example of how convoluted the procedural code can get... I've had a few encounters with it, trying to get the reports converted from FPD2.6 to fit 132 columns on A4 paper, and my head was spinning. Got that thing working, eventually, but... I hope never to have to go there again :).