>>>I have a Foxpro 2.6 project with about 100 screens which I am converting to Visual 3.0B. I keep getting a "line too long" error as which point the conversion process stops. I have to manually convert the 2.6 screen to use shorter text lines and then start all over again. Are there any utilities or fixes to the conversion code which would help me.
>>>Thanks,
>>>Alex Shoob
>>
>>Alex,
>> A suggestion here.. You may as well do the WHOLE conversion on your own... The tools for converting FP 2.x apps to VFP are not that great, but considering you are going from a procedureal language to an Oop based language, there is only so much that will carry over..
>>
>>You are best served by redesigning you app to take advantage of the enviroment...
>>
>>Thanx!
>>
>>Tony Miller
>>Vancouver, Wa
>
>I was afraid that might be might be the case. As usual, it's best to do it right the first time rather that kludging things together. What I have are screens in which a lot of help text is embedded. Any suggestions on help systems that work with VFP? I see Blue Sky's RoboHelp Plus advertised a lot. Any suggestions would be appreciated.
>
>Thanks,
>Alex Shoob
>Modesto, CA

Alex,
If you can take the text and someo how get it into a table (with a structure like a 2.x help file) I know of a product that builds help files (win 3.1/95/NT) from them... It is called help angel..

On the conversion front, you are best to look at redoing the entire app.. Look to design it using OOP techniques, and you will go far with it.. Or if need be, look at the app frameworks available and use one of them.. They will save you time, and help in the learning curve of VFP, but be warned.. There is a curve, just depends on how much of VFP's OOP you want to use..

Have questions, let me know..

Thanx!

Tony MIller
Vancouver, Wa