OK, I’m a little overboard already, so full nine yards… There is always Parallels, which can create Mojave virtual machine or a Windows virtual machine, where you presumably run a Client and use it to connect odbc.
Odbc manager mac os x install#
Can you make it work? And does it still work if you File, Export, Project? And if you install mysql 8 on this computer and get a new odbc driver, can you odbc in? This is also a modular approach in that you can re-copy your data to go live in an instant. Get a new Mac with M1 or M2, if that is the inevitable direction, drop in v19.3 (it’s awesome), and a copy of your structure + data. The other way to approach this, though, is from the other end. And it may look just like what you are used to in that the work you will need to do will be coding 4d. I am saying you might be able to buy + build a solution using a plugin to make this near-seamless and give you more power to handle to an array of possible outcomes, like server computer replacement, hardheaded IT, newfangled hardware, and so on, even if they occur in unpredictable fashion. Do you control this to the extent you can say, for example, Apple or Intel for you next Mac? Did you see other threads where moving to a new Mac gives security errors requiring Terminal commands to beat into submission? Do you control this to decide if you need new authentication method, encryption, etc.? Then, you want to switch from v17 to v19. First, you want to switch from mysql 5 to 8. However, you face an ugly assortment of connectivity issues with this one thing that you probably need to keep working, non-stop.
You have invested in 4D which is phenomenally backwards compatible, plus Partner sub (if I’m reading that right), and you are rightfully confident you could move your setup to v19.
0 kommentar(er)
