Mornin' Alex.

>Great letter.

Thanks :)

>Now. Like you, I also have to port a FPD app to VFP and would welcome your suggetions and any shortcuts you find.

I've done several of these, FPD -> VFP. And I've come to the conclusion that the best thing to do is start from scratch. If the table structures are close leave 'em in tact. And if some of the posting routines still fit stick 'em into methods/events. But if you use views, which I *stongly* recommend, then most of your posting routines are out the window between views and bound controls.

The *easy* part of porting FPD -> VFP is that you already know what the app is supposed to do :0

Cheers!


>
>Alex
>
>
>
>>
>>God Bless Hot'lanta...only took 2 days and 1 interview to get another job at a Fox House. In fact, the company was planning to take their FP2.6 application and recode it into 32 bit. The owner had been contemplating switching to VB, and asked me what I thought about that. I told him!!! And when I was done he said something like:
>>
>>"The guys that have supported VB have only given me generalities as to why it is better. You gave me *specifics* why it is not. Take this job and redo the application in VFP."
>>