======================================= Simon Verona Director Dealer Management Services Ltd T: 0845 686 2300 ========================================
I've not played too much with v5, but the world is going 64 bit and I
can't see the value of migrating to v4 of jBASE - you might as well stay
on 3.4 for 32 bit...
Just my thoughts...
Regards
Simon
=======================================
Simon Verona
Director
Dealer Management Services Ltd
T: 0845 686 2300
========================================
For developers, Windows 7 "Professional" should work as well. This is a step between Home and Business. I migrated most of my systems recently from XP to W7Pro and have had no related issues with any DBMS product. Unfortunately I haven't installed jBase yet but that will be done soon as well.
Since jBase v5 is a 64bit platform, you need to stick with v3 or 4 for 32bit. So my next install is v4/32/W7.
T
I have it on both RHEL 5.6 and Centos 5.8 as well as on Win7Pro(64 bit)
Not a big deal on any, although 'nix installations are a LOT easier than Windows.
Biggest difference is that jBase now runs its own ODBC Server/Client instead of Attunity used on 3.x and 4.x.
The code changes I had to make in moving from 4.x to 5.2 were minor (if any). Biggest thing in any version migration is to remember to set all your environment/configuration variables to match your prior version.
Robert