>v17 is 64 bit only on windows (I believe). On windows there are 32bit versions of v17 up through v17R4. v17R5 is the first 64bit only.
>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? Yes, you can still happily program in 4D like you always have. Use of ORDA is not mandatory. You can do both in the same method. It’s not an "either/or" situation. Tom Benedict > On Oct 10, 2019, at 09:09, Chip Scheide via 4D_Tech <[email protected]> > wrote: > > I have done a conversion from v13 - v16, as an experiment. I had no > problems. > I did not run this for my users. > I did some, but not extensive testing. > > as mentioned elsewhere there are a few things that I believe you can > not resolve without a 32 bit version of 4D (PICTs) from inside 4D, and > v17 is 64 bit only on windows (I believe). > SO you may want/need to go to v15 to resolve the PICT issue before the > final conversion to v17. > > If I am mistaken about the 32 bit/64bit part, or you are *SURE* you > have no PICTs, then you should be able to do the conversion in one step. > > On Tue, 8 Oct 2019 00:46:06 -0700 (MST), Peter.Burgess via 4D_Tech > wrote: >> >> 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? ********************************************************************** 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] **********************************************************************
