Thank you Chip.
The suggestion, from other users and from my local 4D rep in Australia, is for
a 2-step conversion from v11 to v13, then to v17. So, similar to your advice.
I will go that direction, and keep a watch out for PICT files.
Regards,
Pete
-Original Message-
From: Chip Scheide <4d_o...@pghrepository.org>
Sent: Friday, 11 October 2019 05:10 AM
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.
**
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
**