Important Note from American Medical Software:
For 2010 (Version 22), AMS requires Pervasive SQL Summit v10.30 or higher. If you are using an older version of Pervasive PSQL, you should make plans to upgrade as soon as possible. Users of PSQLv11 should apply the v11.01 Update 2 patch or higher for the best results.

QUICK LINKS FOR PERVASIVE PSQL v11 USERS:

• AMS Installation Document for PSQLv11: Our Installation Document is specifically designed to help American Medical Software users get their database software installed quickly and easily. Note that the install documentation for PSQLv10 and PSQLv11 is the same.
• Download Pervasive PSQL v11: This link allows you to download a 30-day evaluation license and patches for the PSQLv11 database engine. Smaller sites (under 5 concurrent users) want the Workgroup Engine. Larger Sites (6+ users) should download the Server Engine instead. AMS recommends downloading both the base install *AND* the Latest Patch Update from Pervasive's web site!

QUICK LINKS FOR PERVASIVE PSQL SUMMIT v10 USERS:

• AMS Installation Document for PSQLv10: Our Installation Document is specifically designed to help American Medical Software users get their database software installed quickly and easily.
• Download Pervasive PSQL Summit v10.31: This link allows you to download a 30-day evaluation license and patched for the PSQLv10.30 database engine. Smaller sites (under 5 concurrent users) want the Workgroup Engine. Larger Sites (6+ users) should download the Server Engine instead. If you are on PSQLv10.20 or older, this same link can be used to patch your engine to v10.31. You MUST have an existing v10 license to apply this patch. If you have PSQLv9 or older, then please purchase an upgrade to PSQLv11 instead.

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 with fewer than 5 concurrent users, then the WorkGroup Engine (WGE) is for you. You need a license for the number of concurrent users, at approximately $50 per user. The database engine and the license goes onto the SERVER, or the computer on which your WINDIR directory resides. All other computers get the Pervasive Client installed to them.

If you need more than 5 concurrent users, then you need to be in the Server Engine instead. The Server Engine has user counts of 6, 10, 20, 50, and more, and it also provides additional performance and security over the Workgroup Engine for these larger systems. Additonally, if you expect to exceed 5 users in the near future, you should get the Server Engine now to save money later on. The Server Engine requires the use of a Windows 2003/2008 or Linux database/file server for best operation, but smaller systems can also work on Windows XP/Vista/7, as long as you don't exceed the limitations from Microsoft on these operating systems. 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 Pervasive PSQL v11 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, Pervasive.SQL V8, and Pervasive PSQL v9. These old engines are no longer supported by Pervasive Software, and AMS has also stopped supporting these releases for their products. If you have an older version, upgrading to Pervasive PSQL v11 is required at this time.

Pervasive PSQL Summit v10 was released in 2007, and is a paid upgrade from older versions. PSQLv10.30 is a recommended minimum running AMS. 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 users must have SP2 to install this release. Users should also obtain the 10.31 patch, indicated above.

Pervasive PSQL v11was released in 2010, and is a paid upgrade from older versions. PSQLv11 is the best platform and is fully supported by AMS at this time. Please note that PSQLv11 software is NOT supported on Windows 2000 or older, so sites with older computers may be forced to upgrade their operating systems first. Also, some patches may be required for other operating systems. Check with Pervasive's web site for requirements.

*Items with a NO are not supported by the application vendor at this time. Items with YES are supported. Items with R are Recommended. Items with no entry are unknown at this time.

There are a few points of interest:

1. Installation Tip: AMS has found a possible conflict with the Cache Engine feature of Pervasive PSQL. 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 Welcome screen, click on the option "Configure Microkernel Router".
   • Click on the heading (on the left) for "Performance Tuning".
   • On the right side of the window, Uncheck "Use Cache Engine" to disable the CCE.
   • Click OK or APPLY, exit the PCC, and restart your computer to ensure that the changes take effect.
2. Performance Tip: If the Workgroup Engine is used, the machine with the data files physically on it (also called the peer server) should be designated as the permanent gateway using the Gateway Locator Utility, which will provide the best performance and stability. See our white paper on this topic for more information, or click HERE for the instructional video!
3. Performance Tip: If you are running an older database and have never upgraded the file versions, you can rebuild your X*.BTR data files to take advantage of even more performance gains. See our white paper on this topic for more information.
4. Status 116 Problem: We have seen some sites with Status 116 errors after upgrading from Btrieve 6.15. If this occurs, 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 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.
6. Status 161 Appearing -- Users are taking TWO licenses: This issue is present in older versions of PSQLv10 and PSQLv11 and has been fixed by Pervasive Software. Please update your environment to the latest patch for v10.31 or v11.01.
7. ODBC Error after moving Pervasive to a new server or upgrading: Some people have been migrating their AMS databases to newer and more powerful servers to obtain better performance. Others have been upgrading to newer versions of the Pervasive database. With many applications, you can simply copy over the data, re-map your workstation drives, and go. However, with the AMS application, you may receive an "ODBC Connection Error", and some additional changes may be required. The following information was provided to us by AMS for your convenience. If you have questions about the process, however, 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.
8. Error message received: Maximum Number of Users Exceeded - Please check all workstations. This error is generated by the AMS application indicating that you have exceeded their internal license count. It is NOT related to your Pervasive database, which would provide an error like "Pervasive SQL's Maximum number of User Licenses has been exceeded." Please contact American Medical Software for details about your product license.
9. Yesterday's Date Appears on the AMS Login Screen: Some sites have experienced problems with the wrong date showing up on the screen. To clear this, shut down all users out of AMS first. Then, start up the Pervasive Monitor on the server and select Microkernel/Active Users. If any users are still showing in here, select each user and click "Disconnect" to drop the database connection. Finally, restart AMS on ONE machine and log in -- this will set the date correctly. To avoid this problem, all users should properly log out of AMS each night, and the first user in the morning should fully log in before other users launch AMS.

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!