Hi Tom, No, it does not use 4D Write. And, yes, I am aware of the 64-bit issue. I’ve just been through this with two of my existing systems and am planning to address this with this system. I will run a 64-bit compatibility audit on it after replace the depreciated-stuff. This client is a non-profit and their funding is limited. My plan is to address the issues to get them stable on v17 and then address the 64-bit and project-mode issues in 2021.
Regards, Ken > On Apr 24, 2020, at 4:35 PM, Tom Benedict via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi Ken, > > Does this app use 4D Write? If it does, and if you ever think this app will > move beyond v17, you gotta think about 64 bit, if you haven’t already. > > Also, Chuck mentioned getting pictures converted, but there’s more to 64bit > compatibility. Would be good to run a 64 bit compatibility audit on it. > Furthermore, if you do go beyond v17 and want to use Project Mode (which I > think is inevitable given that there are features which only work when using > Project Mode; that will only increase over time) your structure also needs to > be Project Mode compatible. You can run Export Structure File in v17r4 or > greater to find out what Project Mode incompatibilities need to be addressed. > This blog post > <https://blog.4d.com/convert-an-existing-database-into-a-project/ > <https://blog.4d.com/convert-an-existing-database-into-a-project/>> includes > a good overview of compatibility issues. If the structure uses Highlight > Buttons, those will need to be manually converted to 3D Buttons. > > HTH, > > Tom Benedict > >> On Apr 24, 2020, at 15:12, Chuck Miller via 4D_Tech <4d_tech@lists.4d.com >> <mailto:4d_tech@lists.4d.com>> wrote: >> >> First, I would not use windows 7 at all. I would move to windows 10 >> >> Second here are some potential ares of concern that you will need to deal >> with >> >> 1. Are there any sub-tables. If so I would recommend creating new tables and >> moving data in v 15 >> >> 2. There are probably obsolete pictures in the db. You can use JPRs >> component in 16 (32 bit mode) >> >> 3. I would also not use the built in primary key stuff, but would add a UUID >> to each table and table that the primary key. I have previously posted code >> I have used to create these. You need to create these with an empty data >> file. When you open an existing data file, all of these keys should be >> populated automatically. If not I have code that will check and make sure >> that all records have UUIDs. >> >> 4. I would also run tools on structure air each in 12 and then at each step >> up to a newer version >> >> Others may tell you that you can use an existing unique key in a table for >> this. I would not, as these are used only for journaling. I would not want >> to make a UUID key on a one table that was used in a many table as the link. >> I would keep all my other long ints for that. >> >> Regards >> >> Chuck >> >>> On Apr 24, 2020, at 5:16 PM, Kenneth Geiger via 4D_Tech >>> <4d_tech@lists.4d.com <mailto:4d_tech@lists.4d.com>> wrote: >>> >>> Hi all, >>> >>> I’m solicitating your opinions. >>> >>> I’ve picked-up a new 4D client. They have an existing 4D system (v12 >>> running on Win7) that has been stagnant for quite e few years. I believe it >>> was originally written under 2004 or maybe even 6.8.5. They’re looking to >>> replace their computers with Win10 machines and and upgrade 4D. I’m a Mac >>> guy and I do my Win development in a VMWare environment. I’ve got several >>> configurations available. I’ve got a Win7 environment that has a 4D v14 >>> installation and a Win10 environment with 4D v15, v16, and v17 >>> installations. My thought is to skip v14 and open the v12 system under v15, >>> take care of what needs to be updated, and then move it to v17. Your >>> thoughts would be most appreciated. >>> >>> Stay safe and healthy, > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > <http://lists.4d.com/archives.html> > Options: https://lists.4d.com/mailman/options/4d_tech > <https://lists.4d.com/mailman/options/4d_tech> > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > <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 **********************************************************************
