In my experience 4D conversions have generally been fairly smooth, and that's going back many versions. When I did a 4D v11 to v15 conversion (Mac server and clients) a few years ago there were no significant issues that I recall. I've recently completed a conversion of that same database from v15 to v17 the task was bigger in that we wanted to deal with the Subtables issue which we ignored in the previous conversion, and also prepare for Object Notation support. In my case, the database had widespread usage of the dot character in variables, method names, table and form names. There were nearly 6000 warnings to address. It was a painful task but I managed it.
Other issues that most conversions will have is converting PICTs to PNG, JPG etc as PICT is now deprecated but it's not difficult. Also, a number of commands are obsoleted and they need to be addressed, either by removal or replacement of more modern equivalents. The biggest issues with any conversion in my experience is the use of 4D Plugins, especially third party ones that may no longer supported. With 4D, 4D Write is now replaced with 4D Write Pro and from what I have read it requires a complete re-write if you use that plugin. I'm sure there are some issues that I forget to mention, but I would say not to be frightened to go for it. Assess the scope of conversion work needed and plan from there. Regards, Narinder Chandi, ToolBox Systems Ltd. I am available for new consulting opportunities… http://4d.1045681.n5.nabble.com/ANN-4D-Developer-Available-td5765443.html -- -----Original Message----- From: 4D_Tech <[email protected]> on behalf of 4D Tech Mailing List <[email protected]> Reply-To: 4D Tech Mailing List <[email protected]> Date: Tuesday, 8 October 2019 at 08:46 To: 4D Tech Mailing List <[email protected]> Cc: "Peter.Burgess" <[email protected]> Subject: Converting 4D Server v11 to v17 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:[email protected] ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
