I like the thought of going from PG -> Scripted SQL file -> FPW Tables.
I understand that there'd be this "Pulling" app the same as that there would be an "Upsizing" app. I have to have an app "Going the wrong way" but it does make sense to have a fall back.
Thanks for the feedback! On 07/15/2015 04:53 PM, Ted Roche wrote:
Wow. Tough question. But a good question. Appreciate a client who thinks about contingencies. IIRC, FPD/FPW could only access SQL Server using a proprietary .PLB/.FLL client-server library. Is it possible to recompile the FPW app in VFP, just recompile, to gain all the benefits of working with VFP, including ODBC? PostgreSQL can be scripted to generate SQL files you could use to repopulate DBFs (I've done this), but if you're working with anything other than ints, floats, booleans, varchars and dates (NOT datetimes) you'll start hitting conversion issues. I'm sure you recognize that migration is another app you write in parallel with the new app you're developing. Two-way migration means two apps :)
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/55a6cafe.8000...@cullytechnologies.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
