A Forum member recently PM'd me after another thread related to the whole 32-bit/64-bit compatibility issue for FTV applications. I didn't get a chance to reply them yet, so I thought I'd do it here as it is relevant to the previous info...
They wanted to know if they had created an application in FTVS v6.10, or above, under a 64-bit OS, could they then send that "64 bit" application to their customer, who is using FTVS v6.10, or above, under a 32-bit OS, and could they successfully restore it?
The simple answer is yes, they could. The fact that both parties are using FTVS v6.10, or above, means they are fully compatible.
The confusion arises here because they are both using the same FTVS version, but under a different OS. Just because FTVS is installed under a 64-bit OS, does not make an application created there a "64 bit" application. As I have mentioned, the MSSQL Server, now used for the tag database, is the 32-bit version, regardless of whether FTVS is installed under a 32-bit or 64-bit OS. So FTVS applications, created under either 32-bit or 64-bit OS, are both using 32-bit tag databases.
So there is no compatibility issues with exchanging FTVS v6.10, or above, applications between 64-bit and 32-bit Operating Systems.
They also mentioned the use of the "Legacy Tag Database Conversion Tool" in relation to the above. I didn't bother getting into it as another option in my last post here, as it was long enough, but I'd like to explain that option now...
Another option for opening and working on a pre FTVS v6.10 application file i.e. v5.0 - v6.0, within a 64-bit OS, is to use the "Legacy Tag Database Conversion Tool".
Note: If you have installed FTVS v6.10, or above, on a 32-bit OS, then the 32-bit WATCOM tag database is already installed, along with the 32-bit MSSQL Server tag database. A v5.0 - v6.0 application should sucessfully restore/open under these conditions.
If you have installed FTVS v6.10, or above, under a 64-bit OS, then to open v5.0 - v6.0 applications, which were of course created under a 32-bit OS, you must first use the Legacy Tag Database Conversion Tool under a 32-bit OS to extract the WATCOM tag database. You then go to the 64-bit OS and run the same Legacy Tag Database Conversion Tool to create the new tag database within the MSSQL Server by using the extracted WATCOM tag database. This then allows the converted tag database, and its application, to be opened for editing under the 64-bit OS.
Again, having XP Mode under Windows 7 Professional greatly assists with this process by providing the two OS environments required to carry out this procedure.
Regards,
George