Hi all. There was a small thread on this topic 12 months ago, overall the reaction seemed to be positive, but given that time has passed and other people may have tried a large 'jump' conversion such as this, I would be very interested in their experiences. In short we have a fairly large database, Windows platform, re-write not feasible, reasonable design with no sub-tables (I say reasonable because it has really only suffered from 2 primary developers and while they may not have been highly skilled programmers at least were not reckless), and we are moving to a Client base running Windows 10 PCs. We really need to upgrade, and preferably to the very latest version, otherwise the risk of some critical failure becomes unacceptable. I would like to gauge how feasible and/or straightforward it would be, to convert from 4D Server v11.9 to v17. Is it mostly just a matter of clicking a button and letting 4D do its thing, or are there some serious pitfalls I should watch out for? In the thread circa October 2018, the suggestion seemed to be that while v17 has a different architecture and is primarily object orientated, it will still accept and interpret v11 style language. Is this truly the case?
Thanks for your time. Regards, Pete -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
