Hi Peter, Unless we’re seriously out of touch, v17r4 is the last version that supports 32bits and thus 4D Write classic. Depending on what you’ve done with it, a major rewrite (pun intended) is required. The code doesn’t translate and any data you have needs to be converted. 4D hasn’t done much to help the migration process. It’s pretty much roll your own.
V17r4 is nice because you can have Write and Write Pro working side by side. We’re in the process of doing this ourselves. Good luck. Paul > On 5 Feb 2020, at 15:37, Peter Jakobsson via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi > > I’m going to be making the leap from v15 to v18. I think the biggest > transition will be moving to 4D Write Pro as I have quite a lot of legacy 4D > Write code to deal with. > > In the meantime, does anybody have experience of migrating big 4D Write > codebases ? What are the major gotchas ? > > Will legacy 4D Write work in v18 in the meantime or do we need to migrate to > 4D Write Pro to even run it ? (When I try it it invokes license privilege > errors everywhere). > > Many thanks for any tips > > Peter > > ********************************************************************** > 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 > ********************************************************************** ********************************************************************** 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 **********************************************************************
