Pervasive PSQL v10.10 - README
General Release - June 2008

Contents

Welcome to Pervasive PSQL v10.10. This readme file contains the following topics:

Installation Notes

This section discusses topics pertaining to the installation of the product.

The software and hardware requirements for Pervasive PSQL v10.10 are listed on the Pervasive Software web site. See http://www.pervasive.com/Database/Products/v10/Pages/RequirementsCharts.aspx

If you have not installed the product and want to read about installation, see the portable document format (PDF) book Getting Started with Pervasive PSQL.

Windows

The following topics apply when you install to Windows.

Subject
Discussion
Windows firewall and client/server applications
The Pervasive PSQL Server and Workgroup installation adds files to the firewall access list to enable client/server functionality. If the operating system security prompts you during installation of Pervasive PSQL to unblock or allow communication with a Pervasive PSQL component, select OK (yes).
If you encounter problems with your client/server applications not working correctly after installation, check the firewall access list or the ports. You may need to adjust some of the security settings to enable client/server applications. You can add files to the access list or open ports. You do not need to do both.
If you want to add Pervasive PSQL components to the firewall access list, add the following:
  • For Pervasive PSQL 32-bit Server, ntdbsmgr.exe.
  • For Pervasive PSQL Workgroup, w3dbsmgr.exe.
  • For Pervasive PSQL 64-bit Server, ntdbsmgr.exe and ntdbsmgr64.exe.
If you want to open ports, Pervasive PSQL communicates via the following ones: 3351 for the transactional interface, 1583 for the relational interface, and 139 for named pipes. Note that opening a port opens it for all access, not just for Pervasive PSQL.
Refer to the operating system documentation on security, firewall settings, and ports.
Default location of installed components
The default location of installed components differs in Pervasive PSQL v10 from previous releases. This change allows the Pervasive PSQL products to adhere to installation guidelines provided by the operating system vendor.
Installation now places files into different root locations depending on product and platform. See “Default Location of Installed Components” in What’s New in Pervasive PSQL for details.
Characters to avoid in installation path
The pound (#) and percent (%) characters should not be used in installation paths for the Pervasive PSQL products if you intend to use Pervasive PSQL Control Center or DDF Builder. Those two utilities will not run if the installation path contains a pound character or a percent character.
FireFox Browser
Note that the Registration page invoked at the end of a Pervasive PSQL installation, register.htm, does not display in the FireFox browser.
The Workaround solution is to open the registration page manually in FireFox. The file is located in installation_location\Pervasive Software\PSQL\Docs.
Upgrading
If you install Workgroup Engine or Client Cache Engine as an application, then later decide you want to run it as a service, uninstall the engine, then reinstall it as a service.
Security Solutions data management products
If you have Pervasive PSQL v10.0 and Backup Agent 1.2, DataExchange 2.9 or AuditMaster 6.4 installed, the Security Solutions products will continue to work after you upgrade to Pervasive PSQL v10.10.
Note, however, Backup Agent 1.2, DataExchange 2.9 or AuditMaster 6.4 cannot be installed directly on Pervasive PSQL v10.10. They can be installed only on PSQL v10.0. They can be used with Pervasive PSQL v10.10 if they were already present after you upgraded from Pervasive PSQL v10.0 to Pervasive PSQL v10.10.
Revised versions of Backup Agent, DataExchange, and AuditMaster are being prepared that can be installed on Pervasive PSQL v10.10. These products will be available in the future.
Service names
The display names of the Pervasive PSQL transactional and relational services have changed. The display name is what you see in Pervasive PSQL Control Center and in Windows Services, for example. The service names—the name that identifies the service to the operating system—remain the same.
Note that, because the service names remain the same, any scripts or applications that start or stop the Pervasive PSQL services should work as before. The service names for the transactional and relational interfaces are still Pervasive.SQL (transactional) and Pervasive.SQL (relational), respectively.
See “Service Names” in What’s New in Pervasive PSQL for details.
Authorization and security
You must have Administrator rights to install Pervasive PSQL.
Depending on the particular account, a local security policy, “Sharing and security model for local accounts,” in certain Windows platforms can adversely affect network logins. Ensure that your policy for “Sharing and security model for local accounts” is set to Classic, which authenticates users as themselves.
PATH location
If you are installing a downloaded version of Pervasive PSQL, do not place the setup files in a location that is listed in the PATH environment variables. This can cause issues with file copying during install. Place the setup files in a location such as the Windows TEMP directory.
Windows 2000 Service Pack
Windows XP Service Pack
Some versions of Windows supported with Pervasive PSQL v10.10 may not have the minimum required version of the Windows Installer installed. Pervasive PSQL v10.10 requires Windows Installer v3.1 be installed in order to run the PSQL installation. To see what version of the Windows Installer is present on your system, type MSIExec /? at a command prompt.
If your version of Windows does not have Windows Installer v3.1 installed, either upgrade your version of Windows Installer or install Pervasive PSQL v10.10 using the Setup executable file, which will automatically upgrade the installed version of Windows Installer to v3.1 before running the Pervasive PSQL v10.10 installation.
Silent install
During an upgrade from Pervasive PSQL v10 automatic updates are applied to fix known issues related to uninstalling Pervasive PSQL v10. These updates are not automatically installed during a silent installation of Pervasive PSQL v10.10. if you are upgrading from Pervasive PSQL v10 to Pervasive PSQL v10.10, using the silent installation method, first install the latest Pervasive PSQL v10 update from the Pervasive web site.
Silent Install Examples
Before upgrading to Pervasive PSQL v10.10 you would run the following:
PSQLv10Patch_Client_x86.msp /qn /l*v "%temp%\PSQLv10_pre-UpgradePatch.log"
After upgrading to Pervasive PSQL v10.10 you would run the following:
{install_folders}\Redist\PVSW\PSQL\Patches\PSQLv10Patch_Server_x86.msp /qn /l*v "%temp%\PSQLv10.10_post-InstallPatch.log"
Updates to the Pervasive PSQL v10.10 that may be supplied with the installation are automatically applied at the end of the installation process. (These files are located in the \Redist\PVSW\PSQL\pathces\ folder. During a silent installation, these updates are not automatically applied. If updates are supplied in this location, apply the updates separately after the Pervasive PSQL v10.10 silent installation completes.
The installation for the Java Runtime Environment (JRE) Standard Edition does not run in silent install mode. If you want to install Pervasive PSQL silently and use Pervasive Control Center or the user documentation, you should first run a JRE installation before installing Pervasive PSQL.
To determine when a silent install has finished, you may use either of the following methods:
1. Modify the command passed to the Windows Installer Process (msiexec.exe) to have the Pervasive PSQL install run with one of the standard UI options such as /qb, /qb!, /qb+, /qb-, /qb, and so forth. More specific information on MSI UI levels is available on the Microsoft Developer Network (MSDN) Library on the Web.
Note that everything after the setup.exe command line option /v is passed to msiexec.exe. See also the Macrovision Helpnet Web site for additional information on how to pass msiexec.exe command line options via the InstallShield launcher (setup.exe).
2. Create a log file during the silent install and then parse the log file. For example, the command line below will create a log file named "PSQL_v10_Install.log" in the TEMP directory.
setup.exe /s /v"/qn /L*v \"%TEMP%\PSQL_v10_Install.log\""
Parse the log file for the string "completed successfully." If this string is found, the silent install has finished.
Windows 2008 Server Core Installation
The optional installation features are disabled by default when installing Pervasive PSQL Server on Windows 2008 Server Core.

Linux

Pervasive PSQL v10.10 supports Linux distributions running Kernel 2.6.0 or higher. For information on installing Pervasive PSQL v10.10 on Linux, see “Installing Pervasive PSQL for Linux” in Getting Started with Pervasive PSQL.

Upgrading to Pervasive PSQL v10.10

If you are upgrading from a previous version of Pervasive PSQL on Linux, you must uninstall and then install Pervasive PSQL v10.10. For information on upgrading to Pervasive PSQL v10.10 on Linux, see “Upgrade Installation” in Getting Started with Pervasive PSQL.

Full and Core Installations

Full and core installation packages are available for Linux. A full installation includes the necessary engine and client files, all available utilities and the complete user documentation. The core installation contains only the engine and client files (or client files only for the 64-bit client).

The following table outlines the installation packages available.

Table 3‑10 Full, Core, and Client Installations for Linux
Pervasive PSQL Product
Installation Type
Contains
Example Name of Package1
Server 64-bit
Full
Engine and client files, utilities, and documentation
Pervasive.SQL-x.yy-zzz.zzz.x86_64.[rpm | tar]
Core
Engine and client files
Pervasive.SQL-Core-x.yy-zzz.zzz.x86_64.[rpm | tar]
Server 32-bit
Full
Engine and client files, utilities, and documentation
Pervasive.SQL-x.yy-zzz.zzz.i486.[rpm | tar]
Core
Engine and client files
Pervasive.SQL-Core-x.yy-zzz.zzz.i486.[rpm | tar]
Client 64-bit
Client
Client files
Pervasive.SQL-Client-Core-x.yy-zzz.zzz.x86_64.[rpm | tar]
Client 32-bit
Client
Client files, utilities, and documentation
Pervasive.SQL-Client-x.yy-zzz.zzz.i486.[rpm | tar]
1 x.yy-zzz.zzz represents the actual digits in the file name that indicate the release and build number of the product

Usage Notes

This section discusses situations you may encounter using the product after installation. See also Known Issues.

Windows

Subject
Discussion
Restore point errors in Pervasive PSQL install log
Failures pertaining to restore point can be ignored. Sometimes the Windows operating system fails to create a snapshot of the current disk (called a restore point) prior to allowing a new application installation. The restore point is not required because the Pervasive PSQL uninstall completely removes the Pervasive PSQL product, rendering the same result as if you had used the Windows restore capability.
System DSN creation on Windows 2008 Server and Windows Vista
You can create system data source names (DSNs) only if logged on as an elevated administrator. A standard user cannot create system DSNs. This is a restriction placed by Windows, not Pervasive PSQL.
When you create a new database with PCC, a corresponding system DSN is created by default. (You can override the default if you choose.)
If you are logged on as a standard user or a non-elevated administrator and attempt to create a system DSN from PCC, status code 7011 results.
As a standard user, you have two choices to create the system DSN for the database. You can use PCC or the Pervasive Distributed Tuning Interface PvCreateDSN() call. You must run the Workgroup Engine in an elevated mode with administrative privilege, or as a service with LocalSystem or administrative privilege.
If you are logged on as a non-elevated administrator, you can also use the ODBC Administrator to create a system DSN locally once you elevate to full administrator.
Once the system DSN is created successfully, any user may start the Workgroup Engine and use the DSN.
Refer to the Windows documentation for security and types of users.
Internet protocol on Windows 2008 Server and Windows Vista
Pervasive PSQL supports Internet Protocol (IP) v4, not IP v6. Consider changing the operating system default configuration from IP v6 to IP v4. Using IP v4 as the default prevents the delay caused by the database engine when it attempts to use IP v6 then must revert to IP v4. Refer to the operating system documentation for setting the IP default.
Right-click shortcut for "Run As Administrator" on Windows 2008 Server and Windows Vista
A right-click on an application utility in the Windows Start menu does not offer a "Run As Administrator" option. This is a limitation of Windows.
If, for some reason, you want to run a Pervasive PSQL utility in an elevated mode, you have several options:
  • Run the utility from an elevate command prompt
  • Create your own desktop shortcut to the utility executable
  • Navigate to the utility executable with Windows Explorer.

Linux

Subject
Discussion
ODBC and Linux
Unix ODBC does not come installed with Red Hat Enterprise 5. If your ODBC application is set to use the Unix ODBC cursor library, you need to install the Unix ODBC package or change your ODBC application to use the Pervasive ODBC driver.

New Features and Enhancements

Refer to What’s New in Pervasive PSQL for a discussion of the new features and enhancements included with this release.

Known Issues

This section lists the known issues for Pervasive PSQL v10.10.

Component Area
Tracking Number
Description
Installation
55835
Installation time on Windows Vista is twice or more slower than non-Vista operating systems on equivalent hardware. Microsoft has confirmed that this is expected behavior because of the increased number of filter drivers such as UAC Virtualization and Vista Search Indexing.
56004
PCC and DDF Builder are not functional when added with install "Modify" operation.
Workaround: Uninstall and reinstall all of PSQL.
57333
When running SuSE 10.1 server with a Windows client, permission errors, access denied errors and login failed errors occur. This is due to SuSE v10.1 installing Samba v3.0.24, which does not include support for Vista/Longhorn.
Workaround: Use the SuSE subscription with YAST2 to install the latest updates and dependencies.
56240
PSQL v10 upgrade install does not disable DX 2.8 services
56018
Install not prompting user to uninstall PDAC SDK
56075
Engines not added to firewall when performing minimum installation.
57224
v10.10 install cannot handle long Java path
57251
No "Repair" option given in windows control panel after install
DevCore
55946
Set data path to ~150 chars and PSQL services not to start
I18N
57338
Fails to bind database with lowercase non-Ascii characters using DTI PvModifyDatabase() function
MicroKernel Engine
56363
Accessing a file using two different symlinks on Windows Vista or Windows 2008 results in status 85 (file locked).
If two applications access a file using two different symlinks, the second open results in status 85 (file locked). For example, if one application opens C:\ProgramData\Pervasive Software\PSQL\Demodata\Class.mkd and another application opens C:\Users\All Users\Pervasive Software\PSQL\Demodata\Class.mkd, the database engine returns status 85.
Workaround: Use the same path for each open to access the file.
Utilities
54785
BDU utility fails when the secured database password is longer than 111 characters.
55396
The PSA functionality “View loaded Pervasive modules” does not list 64-bit Pervasive PSQL components.
56842
CNVDDF.exe returns status 357 and will not convert dictionary
Utilities (Butil)
57217
butil crashes on Linux when incorrect -endbu parameter is used
57334
butil @commandfile does not utilize quoted paths correctly
Utilities (DDF Builder)
54446
DDF Builder does not support creating a table definition for a file that uses ISR (International Sort Rules). DDF Builder does not currently provide a warning.
How to determine if a data file uses ISR:
When a key has one of the ACS flags set, look at the 265 bytes for that ACS.
If the signature byte is 0xAC, then it's a User-defined ACS.
If the signature byte is 0xAD, then it's a locale-specific ACS.
If the signature byte is 0xAE, then it's an ISR.
55960
DDF Builder encounters error when operating on files that are held open exclusively by another process.
Workaround: Ensure that the files are not held open exclusively by another process.
56634
DDF Builder creates an invalid definition for an overlapping segment file
56681
Invoking DDF Builder plug-in details on 64-bit Linux results in internal error
56633
DDF Builder should not allow saving a file with more than 119 indexes
57056
Create Btrieve File\Key Specification Page isn't scrolling.
57070
In VM environment, SQL index pane is very small or can barely be seen.
57077
DDF Builder does not show preview values for GUID
57088
DDF Builder does not complain when you try to create a definition on a file with 1 multisegmented key
57093
Help link for Table Definition Editor throws an error dialog
57111
DDF Builder will not import btrieve schema remotely against demodata
57255
Window DDF Builder does not recognize 5x files on remote Linux servers.
57271
Cannot export Btrieve Schema from a remote machine using DDF Builder
57335
DDF Builder prompts multiple times for owner name on tables with owner names during database check even if you cancel the operation
57343
Problem importing Btrieve schema remotely using DDF Builder
Utilities (PCC)
56779
PCC crashes in FedoraCore8 on Linux when adding a new table.
This is caused by a known bug in Sun's JRE.
Workaround: turn off some features using the following command:
sed -i 's/XINERAMA/FAKEEXTN/g' $JAVA_HOME/lib/i386/xawt/libmawt.so
54990
Some configuration settings in PCC are missing from a virtual network computing (VNC) session.
Workaround: To configure the database engine, use PCC directly on that engine's console or use a remote desktop tool other than VNC.
55321
PCC grid cannot display tables with numerous fields.
Workaround: Use views or SELECT statements to limit the number of fields displayed in the grid.
57195
On SuSE 10.1 x64, when running PCC or DDF Builder you may encounter warnings such as the following:
"Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported"
These warnings can be ignored as they should have no affect on PCC or Builder operation.
On SuSE 10.1 x64, when running PCC or DDF Builder, menu options may be unavailable or greyed out.
Workaround: In the system Control Panel, select Themes and select a theme that is not the system default.
57310
On SuSE 10.1 PCC may abort with message "line4: 5502 Aborted". This is a known system issue with SuSE 10.1 GTK controls.
57345
Error refreshing grid after adding a row in PCC
56855
'Master' login name does not show in PCC on Linux as it does on Windows
56857
One-column select in PCC on Linux results in grid taking the entire space instead of the width of the column data
56878
COLLATE once specified in PCC is not removed on deletion
57210
PCC F10 hot key to Execute All SQL Statements does not work on Linux
57230
Can't execute a view right after you create it in PCC
57257
Progress dialog displayed when loading data in the grid has unusable cancel button
SQL
54781
Executing a stored procedure that contains a print statement inside the PCC or any other GUI tool (such as ODBCTest) may cause the tool to hang.
Workaround: Modify the PSQL Relational Engine service property to "allow service to interact with desktop." This option is configurable with the "Log On" pane under the service's "Properties" screen.
57253
Records are displayed as "#Deleted" instead of actual values when opening them through MS Access 2007.
Refer to the Microsoft Help and Support for information regarding an update for MS Access.
55807
DROP DATABASE disables user session. Any attempt to switch to another database fails.
57372
Relational engine converts I18N Characters to upper case.
57345
SQL Engine not matching index definition to existing Btrieve key
57076
Data pulled from cross databases of different encodings is corrupted
57216
Database Code Page setting change doesn't take effect until all connections are closed
57362
When doing ODBC translation for UTF8 database, space padding is not adjusted
56863
Attempting to create a client DSN from 10.10 client to v9.50 server fails
57274
Stored procedure out parameters crash server
56108
On Linux, creating a user with a password of length 129 or greater is crashing the engine.
57330
Set owner to a value longer than 24 characters returns an erroneous message.
57385
SQLForeignKeys() incorrectly returns HY000 instead of HY009 with invalid use of NULL pointer
Data Archival
55919
Archival logging does not work when a client machine has "use cache engine" turned on and Workgroup Engine or Cache Engine configured to run as a service.
Workaround: Configure the Workgroup or Cache Engine service to run under a username/password that has the necessary rights to access objects on the remote server machine.
System Driver
56575
XIO is not supported in the Microsoft cluster environment
Software Development Kit (SDK)
55423
PvCopyDatabase() does not work for database with referential integrity (RI), regardless of RI level. PvCopyDatabase API cannot properly copy tables with RI constraints. The copied tables with RI constraints return status 73 on open attempts.
55994
Pervasive OLEDB Provider does not work with a database under "mixed" mode security.
Workaround: Use MSDASQL Provider instead.
56481
After completion of the ADO.NET design time installation, ADO.NET 3.0 provider does not appear in the Add Reference list.
56968
DTO won't set a DBCodePage other than UTF8
57265
Remote Window DDF Builder cannot see large file with extension going against linux server

Technical Support

You may obtain technical support from the following Web-based support options:

Windows 2008 Server Certification

Pervasive PSQL is Certified for Windows 2008 Server (64-bit editions). As part of the certification requirements, the following topics are included in this readme file.

Files Not Digitally Signed

The following files installed with the Pervasive PSQL v10.10 products on Windows platforms are not digitally signed.

File
Vendor
Product
Description
keyhh.exe
KeyWorks Software (www.keyworks.net)
KeyHH
KeyHH augments HTMLHelp, a help development environment from Microsoft that produces .chm files from HTML-based source. KeyHH can be used in addition to, or as a complete replacement for, HH.EXE, which is provided by Microsoft. KeyHH provides all of the functionality of HH.EXE, offers solutions for some known bugs in HTMLHelp, and provides additional functionality.
mfc80.dll
MFC80ENU.dll
MFC80JPN.dll
mfc80u.dll
mfcm80.dll
mfcm80u.dll
msvcm80.dll
msvcp80.dll
msvcr80.dll
Microsoft (www.microsoft.com)
Visual C++ 2005 SP1 Libraries
Installs runtime components of Visual C++ Libraries required to run applications developed with Visual C++ SP1 on a computer that does not have Visual C++ 2005 SP1 installed.
localfile_1_0_0.dll in org.eclipse.core.filesystem.
win32.x86_1.1.0.v20070510.jar
swt-awt-win32-3347.dll in org.eclipse.swt.win32
.win32.x86_3.3.2.v3347a.jar
swt-gdip-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
swt-wgl-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
swt-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
swt-xpcominit-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
swt-xulrunner-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
update.dll in org.eclipse.update.core.win32
_3.2.110.v20070615.jar
win32refresh.dll in org.eclipse.core.resources.win32
_3.3.0.v20070226.jar
Eclipse Foundation (www.eclipse.org)
Eclipse Platform Software Development Kit (SDK)
Eclipse Platform SDK's Windows native libraries
awt.dll, axbridge.dll
cmm.dll
dcpr.dll, deploy.dll, dt_shmem.dll, dt_socket.dll
eula.dll
fontmanager.dll
hpi.dll, hprof.dll
instrument.dll, ioser12.dll
j2pcsc.dll, j2pkcs11.dll, jaas_nt.dll, java-rmi.exe, java.dll, java.exe, java_crw_demo.dll, javacpl.cpl, javacpl.exe, javaw.exe, javaws.exe, jawt.dll, JdbcOdbc.dll, jdwp.dll, jli.dll, jpeg.dll, jpicom.dll, jpiexp.dll, jpinscp.dll, jpioji.dll, jpishare.dll, jsound.dll, jsoundds.dll, jvm.dll
keytool.exe, kinit.exe, klist.exe, ktab.exe
launcher.exe
management.dll, msvcr71.dll
net.dll, nio.dll, npjava11.dll, npjava12.dll, npjava13.dll, npjava14.dll, npjava32.dll, npoji610.dll, npt.dll
orbd.exe
pack200.exe, policytool.exe
regutils.dll, rmi.dll, rmid.exe, rmiregistry.exe,
servertool.exe, splashscreen.dll, sunmscapi.dll
tnameserv.exe
unpack.dll, unpack200.exe
verify.dl
w2k_lsa_auth.dll, wsdetect.dll
zip.dll, zipper.exe
Sun Microsystems (www.sun.com)
Java Runtime Environment (JRE)
The JRE is a set of computer software programs and data structures that use a virtual machine model for the execution of other computer programs and scripts.

Windows Installer Custom Actions

The technical details of each Windows Installer Custom Action executed during the PSQL installation process are available to System Administrators. This information is listed in the document PSQL_CA_Reference.rtf, which is embedded in the PSQL MSI installation packages.

Administrators can view and print the RTF content from the "Custom Action Reference" dialog which is only displayed during an Administrative Installation. An administrative Installation can be launched the following ways.

Using InstallShield Launcher Program (Setup*.exe)

  1. Click Start -->Run --> {path}\SetupInstallType_xPlatformType.exe /a
  2. Click Next to display the Custom Actions Reference dialog.
  3. Click Print to print the RTF document.

Using Microsoft Windows Installer (MSI) Process Only

  1. Click Start -->Run --> msiexec.exe /a {path}\PervasivePSQLv10_InstallType_xPlatformType.msi /l*v {path}\LogFileName.log
  2. Click Next to display the Custom Actions Reference dialog.
  3. Click Print to print the RTF document.

Log Files Stored at Root

The Pervasive PSQl Server installation stores the following log files on the system drive in the folder C:\exts:

Files Requiring Administrator Privileges

The following files require Administrator privileges to run.

Files Not Installed To The Applications Directory

The following files do not install to the applications directory:

Files Without Valid Version Information

The following files, which are part of the Java Runtime Environment (JRE), do not contain valid file version information:

Icon Resource Files With an EXE File Extension

Microsoft Windows Installer (MSI) contains icon resource files with a file name extension of “exe.” Note that these files, despite the file name extension, are not executable files.

Such files are located in the %windir%\Installer\{install_type_product_code}\ directory.

For example, in that directory you might see files with names similar to c:\Windows\Installer\{0A3238D7-AC64-1010-B717-F3E3F18B4A8C}\ARPPRODUCTICON.exe and c:\Windows\Installer\{0A3238D7-AC64-1010-B717-F3E3F18B4A8C}\pvswDocsShortcut.A01E0590_D2E0_43CE_B351_BB16EA0FBDE0.exe.

Disclaimer

PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH THE TERMS AND CONDITIONS OF THE ACCOMPANYING LICENSE AGREEMENT.

Copyright ©2008 Pervasive Software Inc. All Rights Reserved.

Pervasive Software Inc.
http://www.pervasive.com
12365 Riata Trace Pkwy, Bldg B
Austin, TX 78727 USA
Voice: (512) 231-6000
Fax: (512) 231-6010
Online Pervasive Contacts

*** END OF README ***