Zen Applications – Be aware of what applications you have currently using previous versions of Btrieve or Zen in your environment. Remember to include both client and server-based applications.Zen Applications – Be aware of what applications you have currently using previous versions of Btrieve or Zen in your environment. Remember to include both client and server-based applications.Zen Ecosystem Products – Existing installations of AuditMaster, Backup Agent, or DataExchange working with the version of Zen to be upgraded must first be uninstalled. Before removing them, we recommend you capture their configuration settings to use in reinstalling and configuring their new versions after upgrading.Vendor-Specific Information – Check with your application vendors for any specific information regarding their product with Zen.TCP/IP Protocol – Make sure that TCP/IP network is configured correctly (you should be able to ping the server by name), and that any firewalls between the clients and server (including firewalls on those computers) are configured to pass database traffic. See Windows FireWalls.DOS Requester – DOS applications are supported only via the BTRBOX requester. Migrate native DOS machines to a Win32 platform before upgrading Zen. BTRBOX and DOS applications are not supported on 64-bit Windows platforms.New Features and File Rebuilding – To make use of new features, you may need to rebuild data files to the newest format version. See the Rebuild utility in Advanced Operations Guide.Data File Backups – Before upgrading, make sure you have a current backup of your data, database engine files, and configuration settings.Scenario | Discussion |
|---|---|
You have existing DSNs created with a version before Pervasive.SQL 2000i SP4 | You must delete all existing DSNs before you upgrade. Once you have upgraded, recreate the DSNs to access the existing databases. New DSNs should connect to a named database, not to an Engine DSN because Engine DSNs are deprecated. See ODBC Connection Strings in ODBC Guide. |
You have existing DSNs created with Pervasive.SQL 2000i SP4 or a later version | You can access your databases by connecting to the existing DSNs. Note, however, the recommendation is that new or revised 32-bit applications should connect to a named database, not to an Engine DSN because Engine DSNs are deprecated. If you want to port your 32-bit application to 64-bit, then make the following changes. •If the application uses DSN-less connections that connect using “Pervasive ODBC Client Interface,” change the connection string to “Zen ODBC Interface.” •If the application uses Engine or Client DSNs, you must create 64-bit DSNs that connect to a named database. Also note that on 64-bit Windows operating systems, 64-bit system DSNs are distinct from 32-bit system DSNs because of the registry design. See ODBC Connection Strings in ODBC Guide. |
You do not have any DSNs defined | For details about creating DSNs, see DSN Setup and Connection Strings in ODBC Guide. If you want to use DSN-less connections for 32-bit applications, use the connection string “Pervasive ODBC Client Interface” and connect to a named database. For 64-bit DSNs, use the connection string “Zen ODBC Interface” to connect to a named database. |