Actian Zen (Pervasive/PSQL) Product Support Lifecycle and Service Packs:

 

Updates and Service Packs (general)

Actian document portal

Evaluation downloads

Actian support

 

Latest V15, V14, V13, V12, V11, V10, V9 and V8 service packs:

 

Actian Zen (PSQL) v15 was published August 2021.

V15 information

 

Actian Zen (PSQL) v14 was published August 2019.

V14 information

Note: we do not recommend use of the backup agent that is bundled with newer installations

 

PSQL v13 was published June 2017 and is being referred to as Actian Zen

NOTE: the Vx Server 13 version is not recommended and is not supported.

Not yet in widespread use, not yet tested by us; as far as we can tell has no advantages that will be of benefit to users of our software.

 

 

PSQL v12 SP1 was published June 2016. Referred to as Actian PSQL 12.

NOTE: the Vx Server 12 version is not recommended and is not supported.

Supported operating systems now includes Windows 2016 and Windows 10.

 

NOTE: PSQL Vx Server 11 which was published in January of 2012 is NOT recommended (although it will work subject however to potential/occasional licensing issues). Users should instead use PSQL v11 (or equivalent older PSQL versions). Vx Server 11 is also NOT part of a normal upgrade path for a Pervasive PSQL v11 or prior user using one of our products. Please do NOT buy it without first checking with us. Call or contact us for further information. Whenever you are considering the purchase of Pervasive software for use with a software product that we publish or support, contact us first to ensure compatibility. The same is true with new operating system releases, potential hardware compatibility issues, etc. Most things will work, but it is dangerous to assume that just anything will.

 

PSQL v11 SP3 was published January 2013 and provides Windows 8 (and Windows 2012 server) specific feature support.

 

PSQL v11 SP2 was published March 2012 and there are no known issues in using this service pack with Advanced Accounting/TAS applications.

 

Supported operating systems now includes Windows 2012 and Windows 8.

Actian support ended July 1, 2016.

 

V10 trial/updates with Vista/Win 7/Win 2008 support, 64-bit transactional engine, first available 9/18/07, SP3 available 9/22/10

 

Note: V9 no longer supported as of Jan. 1, 2010 and no longer generally available as of July 1, 2009. The 9.50.007 (SP2), 9.52 hotfix and 9.71 (SP3) updates are no longer readily available; if you need these updates, please contact us.

 

V9 SP3 release 9.71 (included SP1 and SP2; 9.5 must be installed first; update 1, 9.7 rel. November 2008; update 2, 9.71 rel. April 2009)

V9 SP2 release 9.5 May 2006 (SP2 update 1, Nov 2007; update 2 i.e. 9.52 June 2008 is included in 9.71)

V9 SP1 release 9.1 June 2005 (included in 9.7)

 

8.7 August 2005 (V8 users only need to install this SP to update their system - this update is no longer readily available; contact us if you need this update)

Note: V8 is no longer be supported by Pervasive (as of Jan. 1, 2007)

 

V12 was released by Pervasive on December 17, 2014.

If you are updating to Advanced Accounting 8 or if you are currently running a TAS/Advanced Accounting 6.1, 5.1, 5.0, 4.0 or even 3.0 system, please read the above FAQ document. Any legacy BTRIEVE.EXE system could potentially be improved using Pervasive Software in addition to Windows-based apps written in TAS 6, TAS 7, TAS 7i, Clarion or other programming languages.

Since the summer of 2002, after having supported Btrieve (now Pervasive) based systems for nearly 15 years, we became a Pervasive reseller initially at the urging of one or our customers. Thanks to the input from another customer, we realized that Pervasive.SQL was an exceptional solution for any of the legacy systems running BTRIEVE.EXE (5.10a) or BREQUEST/SERVER, including any system based on TAS 4.x, TAS 5.0, TAS 5.1x running in "DOS" mode or Advanced Accounting 4.x, Advanced Accounting 5.0 or Advanced Accounting 5.1x.

In the DOS-based era which obviously continued into the Windows era, we regularly worked with systems using BTRIEVE.EXE (the most notable being 5.10a which remains in use today) and in BREQUEST/BSERVER implementations, often in wide area network systems. In so doing, we had to acquire some level of expertise with the maintenance, repair, recovery and back-up of these systems even though our primary focus relates to commercial and private software development/programming services.

In August of 1996, Business Tools released Advanced Accounting 5.1 which had a Windows mode using a 16-bit version of Btrieve. Still running today, we support it on systems running Windows 2000, XP and Vista.

In 1997, using the Smithware ActiveX Controls for Btrieve, we interfaced to Windows-based Btrieve via Visual Basic 4 and 5, for an in-house and commercial systems. Our experience with 16-bit and 32-bit Btrieve 6.15 began at this point. We also used Smithware Crystal Reports and later other versions of Crystal Reports.

We began to have experience with systems using Pervasive.SQL (then version 7) in about 1999 and later in resolving conflicts created with Pervasive.SQL 7 installations and DOS/BTRIEVE.EXE systems.

Starting in late 2000 and initially deployed by March of 2001, we completed the first ever TAS 6 system which interfaced innately with Pervasive.SQL data files. Meanwhile we also supported and provided commercial and custom programming for an accounting system that used Pervasive 2000/2000i.

By the summer of 2001, we completed and released on behalf of a third party the first commercial software system written in TAS 6. It used the Btrieve 6.15 engine and we researched and wrote extensive documentation relating to all of the required Microkernel settings (Btrieve 6.15 does not automatically configure itself like Pervasive does).

We have been involved in creating some Peachtree interfaces (Peachtree used the 6.15 Btrieve record manager through 2006 and thereafter switched to Pervasive 9). We have considerable experience resolving Pervasive.SQL and Btrieve 6.15 conflicts as a result (and in working with recent Peachtree releases that create hybrid Pervasive 9.1 installs).

Meanwhile we deployed fully GUI applications written in TAS 6 that interface with Advanced Accounting 5.1 using Btrieve 6.15 and with DBA Software (which uses Pervasive.SQL as its record manager), and later with TAS Premier 7i.

Pervasive.SQL (now Actian Zen) is now the database engine of choice for use with Advanced Accounting 6.1, 7i, 8 and higher (published exclusively and supported by us) as well as all applications written in the TAS 5.1 (and 4.0 and 5.0), TAS 6 and Addsum TAS 7 releases. Pervasive 2000i, V8 , V9 and V10 have all worked worked very well with our applications.

While most of our customers are located elsewhere, Addsum was for many years the only VAR channel for Pervasive software located in the state of Utah.

As of November 30, 2008, due to contractual channel agreements, Pervasive was unable to continue to offer product discounts to VARS like us. Because our focus has always been on the support and consulting of Pervasive and Btrieve products used in conjunction with specific products that we directly support and for which we provide computer programming services, this means that nothing really changes. For suggestions as to vendors from which new, upgrade and count increase products can be purchased, please contact us. And we can continue to assist you with implementation/migration and general consulting with respect to configuration and other technical issues relating to your Btrieve/Pervasive record manager engine.

Our users have successfully used V10 in Windows 2008 Server and Windows 7 workgroup environments. The use of the 64-bit version on 2008 Server seems to work without issues with attached 32-bit clients (XP Pro or Windows 7). Through late 2010, many users continue to use legacy 16-bit Btrieve 5.10a in 32-bit environments (including Win 7 32-bit and Win 7 64-bit using the Windows Virtual PC), Btrieve 6.15 legacy 32-bit, Pervasive 8 (up to Windows 2003 Server and XP Pro clients), and primarily Pervasive 9 through the latest patches (although V10 is required for Windows 2008 Server). Version 11 has been successfully and extensively used since its late 2010 release with XP Pro, Windows 7 and Windows 8 as well as in Server 2008 and Server 2012 environments. Since then we have had users successfully deploy every subsequent release through the current v15.