Renoir,

I had a BIG problem with ReFox and old DOS code - it SHOULD have handled it, but all the PRGs were procedure files (multiple functions) and they terminated after the first procedure.

Frankly, I'd push the client to convert, telling him that "With most of the source code available we have an excellent model for re-writing and upgrading validation code while still moving the application into the world of Windows Connectivity". Followed by talking about MailMerge to Word, automatic emails, etc.

Barbara

>Barbara,
>
>Thanks again! Now for the kicker... It appears that not all the source code is available. IYHO, do you think ReFox can handle this or should I think more seriously about pressing the client to convert to a new platform? The program works well, it just can't currently be modified.
>
>Renoir
>
>>Renoir,
>>You're right where I was 3 weeks ago! We found that the SCO-Fox code will run ALMOST without changes on FPD2.6. The differences we found were on the key codes - inkey() assigned values were different. Ours used a lot of 'graphic' characters to draw boxes and we had to change these, also the UP-Arrow, DN-Arrow, PgUp, PgDown etc.
>>
>>Barbara
>>
>>>Barbara,
>>>
>>>Thanks! The conversion to VFP6 makes sense. I'm now confused as to what I'm looking at from the client. They are running FPD26 using these FRM files. If they were UNIX based when written, how are they running on the DOS system? Am I able to modify and compile the application files (FXP, etc) in FPD? I have almost no experience with UNIX other than LST (or some command like that) so forgive me if this is a really basic topic...
>>>
>>>Renoir