Important Note from American Medical Software:
Effective 3/1/2008, AMS will only support Pervasive SQL Version 9.52 or higher.
If you are using an older version of Pervasive SQL, you should make plans to upgrade as soon as possible. Version 9.52 is required and Version 10.01 or higher is recommended.

QUICK LINKS FOR PERVASIVE PSQL SUMMIT v10 USERS:

• Installation Document for PSQLv10: Our Installation Document is specifically designed to help American Medical Software users get the software installed quickly and easily.
• Download 10-Day Evaluation License of Pervasive PSQL Summit v10: This link allows you to download a 10-day evaluation license of the PSQLv10 database engine. For smaller sites (under 5 concurrent users), you will want to get the Workgroup Engine. Larger Sites (6+ users) should get the Client/Server Engine instead.
• Download Pervasive PSQL Summit v10 Update 1 (v10.01): This updates your v10.0 installation to v10.01. You MUST be on v10.0 to apply this update. See notes about this on our v10 page.

QUICK LINKS FOR PERVASIVE PSQL v9 USERS:

• Installation Document for PSQLv9: Our Installation Document is specifically designed to help American Medical Software users get the software installed quickly and easily.
• Download 30-Day Evaluation License of Pervasive PSQL v9: This link allows you to download a 30-day evaluation license of the Pervasive PSQL v9 database engine. For smaller sites (under 5 users), you will want to get the Workgroup Engine. Larger Sites (6+ users) should get the Client/Server Engine instead. NOTE: The AMS Version 18 and 19 CDROMs contain a copy of the Workgroup Engine download already. If you have this CDROM, browse to the \PVSW_WG_30_Day_Trial directory and install from this location to save yourself some downloading time.
• Download Pervasive PSQL v9 Service Pack 2 (v9.5): This updates your v9.0 or v9.1 software to the v9.5 release. Sites which purchased Pervasive PSQL v9 PRIOR to APRIL, 2006 should get this update. DO NOT DOWNLOAD if you have PSQLV8, unless you want to pay for an upgrade license as well!
• Download Pervasive PSQL v9 Service Pack 2, Update 1 (v9.52): This updates your v9.5 installation to v9.52. You MUST be on v9.5 to apply this update. See notes about this on our v9 page.

The American Medical Software application uses the Pervasive database engine to provide world-class performance and flexibility to their application development efforts. At this time, AMS is not selling this software directly, and they are referring users to resellers such as Goldstar Software to obtain the correct licenses. We have worked extensively with AMS over the years and are in an excellent position to help you get your software installed and running quickly.

Installation of the Pervasive database is easy -- pop in the CDROM & follow the prompts, then reboot, so you can do it yourself or have your tech guy (or gal) handle it for you. There is also a trial download available from the Pervasive web site (see links above) if needed. This trial can be converted to a full license, if you wish to avoid shipping costs of the physical CDROM.

If you have a small site, then the WorkGroup Engine (WGE) is for you. While you can install it on as many computers as you buy licenses for (the server should have a license as well), it only supports a maximum of 5 concurrent users using the database. However, the WGE is a very cost-effective way to get the benefits of the latest Pervasive database for smaller sites.

An upgrade to Pervasive's Client/Server Engine (CSE) provides these same benefits to the larger sites, with user counts of 6, 10, 20, 50, and more. The CSE also provides additional performance and security over the WGE, and should be considered even for smaller sites looking to grow in the future. The CSE requires the use of a Windows NT/2000/2003, NetWare, or Linux database/file server. We also recommend making sure that you meet the Pervasive.SQL Pre-Requisites list on your network before upgrading.

For pricing, please refer to our price list for Pervasve PSQL v10 or call for an exact quote!

Older versions of AMS worked on older versions of Pervasive, including the (very old) Btrieve 6.15, Pervasive.SQL 2000i, and Pervasive.SQL V8. These old engines are no longer supported by Pervasive Sofwtare, and AMS has also stopped supporting these releases for their products. If you have an older version, upgrading to Pervasive PSQL Summit v10 or higher is required.

Pervasive PSQL v9 is a current release, and is a PAID upgrade for any users of older versions. AMS now requires v9.52, which is an updated patch release available directly from Pervasive Software's web site. This release is supported on Windows 98SE or newer, although if you intend to run on Windows Vista, please note that there will be some manual configuration steps. Contact Pervasive Software for more information on these steps.

Pervasive PSQL Summit v10 is the newest release, and is also a paid upgrade from older versions. PSQLv10 is the best platform if you intend to be running Windows Vista. However, the PSQLv10 software does NOT support running on Windows 95, 98, ME, or NT, so sites with older computers may be forced to upgrade their operating systems first. Also, please note that Windows 2000 users must have SP4, and Windows XP uysers must have SP2 to install this release. Users should also obtain the 10.01 patch, indicated above.

*The abbreviations used on the columns above include the Workgroup Engine (WGE) and Client/Server Engine (CSE). Not all engines exist in all versions, and these are marked with N/A. Items with a NO are unsupported; items with YES are supported. Items with NR are not recommended; items with R are recommended. Items with no entry are unknown at this time. P indicates that testing is in progress for this release.

There are a few points of interest:

1. Installation Tip: AMS has found a possible conflict with the Cache Engine feature of Pervasive.SQL. After installation of the WorkGroup Engine (or the client components in a Client/Server Engine), you should disable the Client-Side Cache feature by following these steps from each computer on your network:
   • Start the Pervasive Control Center (Start/Run/PCC.EXE)
   • On the left hand side, click the plus signs for Pervasive.SQL Engines, your workstation, Configuration, and Client. (PSQL9 users open the Microkernel Setup" item instead.)
   • Click on the entry for "Performance Tuning".
   • On the right side of the window, double-click on "Use Cache Engine" and change the setting to OFF.
   • You should now restart your computer to ensure that the changes take effect.
2. Performance Tip: If the WGE is used, the machine with the data files physically on it (usually known as the peer server) should be designated as the permanent gateway using the Gateway Locator Utility. (If this is on a separate server, then you will need to purchase a database engine license for this computer as well.) Changing the configuration from a floating gateway (the default) to a permanent gateway will provide the best performance and stability. See our white paper on this topic for more information, or click HERE for the video!
3. Performance Tip: After your system has been running on the new engine for a few weeks, and you are comfortable enough that you will never go back to the old version, you should rebuild your X*.BTR data files to take advantage of even more performance gains. See our white paper on this topic for more information. If you have a very old database with 5.x files, you may be REQUIRED to rebuild files to maintain compatibility with PSQLv9 or newer.
4. Status 116 Problem: We have seen some sites with Status 116 errors after installing. If you run the application and do NOT see the Pervasive.SQL splash screen, then you may have an old DLL still stuck on your system. Search the local and network hard disks to locate a files in the following list: WBTRCALL.DLL, WBTRVRES.DLL, WBTRLOCL.DLL, WBTR32.EXE, WBTRV32.DLL, W32BTICM.DLL, WBTRTHNK.DLL, W32MKDE.EXE, W32MKRC.DLL, dated 1999 or older. If you find such a file, rename or delete it. Do NOT delete any copies in the C:\PVSW\BIN folder. (Copies in the PVSWARCH directory have been found and successfully archived by the installation process. You may leave these copies alone, and after a few weeks, you can safely remove this entire directory structure.)
5. Status Code 2738 During Installation: Some users are experiencing this error on certain computers, especially on older Windows 98 computers. This error message indicates that the Microsoft Installer was unable to run the VBScript needed to install the product. If you get this message, you will need to download and install the VBScript update utility from Microsoft, reboot your computer, and then try the installation again.
6. Status Code 161 After Installation: If you are getting a Status 161 (Licensing Error) after installing Pervasive, then your database license may not be properly applied. On each computer, start the Pervasive License Administrator (which you'll find in the Start/Programs/Pervasive programs group) and check the license count showing on this screen. If you do not see a permanent license with the correct user count, then you will need to apply your license. See your invoice or packing slip for your Registration Keycode, and enter this string into the boxes provided, then click "Add License". You should then see the proper license count.
7. ODBC Error During AMS Installation: AMS has found a problem with the Pervasive PSQL v9.5 Installation that provides two modules (DLL's) that are slightly out of date. The Pervasive code provided on the AMS installation CDROM has been updated to include the new files, but if you have installed from the original Pervasive CDROM, you may not have these files. After installing PSQLv9.5, please download THIS FILE and unzip it into your C:\PVSW\BIN directory. Contact AMS for more information on this issue.
8. Is Pervasive PSQL v9 supported on Windows Vista? Windows Vista adds a whole new level to the security game. See the Pervasive/Vista white paper for more details on getting PSQLv9 to run on this operating system. Instead, you may wish to purchase PSQLv10, which is natively supported.
9. Moving Pervasive to a new server: Some people have been migrating their AMS databases to newer and more powerful servers to obtain better performance. With many applications, you can simply copy over the data, remap your workstation drives, and go. However, with the AMS application, some additional changes may be required when you do this. The following information is provided for your convenience only. If you have questions about the process, please contact AMS directly for help.
   The ODBCADMIN.EXE application, located in the AMS application directory, can be used to move the data from one server to another. This tool properly creates the ODBC DSN (required for AMS to work properly) and also populates the XODBC.BTR file with important information to help the workstations find the server as well. You can safely delete this XODBC.BTR file from your database and this tool will re-create it with the new data.
10. Problems with Backups on PSQLv10: Some sites have seen some problems when running on PSQLv10 with their backups, since the database engine erroneously holds files open that it should be closing. You may wish to update to v10.01 or higher, or use Continuous Operations Mode or Backup Agent to obtain proper backups.

If you need help with installing or patching your database engine, Goldstar Software also provides update services via the Internet for a fixed fee. See our Installation Services page for more details. If you are running PeachTree Accounting, then we strongly recommend using our installation services, as PeachTree can make installing a bit more of a challenge.

If you are a software vendor and would like to add, remove, or modify your information on these pages, we'll be happy to oblige. Simply contact us directly!