DBA Classic FAQ

What is DBA Classic?

DBA Classic was our first product and was originally named "DBA Manufacturing." It was introduced in 1992 as a DOS-based product and was converted to run on Windows in 1997. When we introduced our current product, "DBA Manufacturing Next-Generation" in 2003, the original product was renamed "DBA Classic" so that it would not be confused with our new product.

What is the status of DBA Classic?

We discontinued development of DBA Classic in 2002 and ceased providing technical support in 2006.

How can I get support for DBA Classic?

We discontinued providing technical support for Classic in 2006. If you need support for a technical problem we suggest you perform a web search on "DBA Classic Support" to obtain a listing of third parties who continue to provide support services for DBA Classic.

How do I buy additional Classic users?

Additional user licenses for Classic are still available and qualify for free matching Next-Gen users, should you someday transition to the new product. Click this link for details.

Classic Additional User Pricing »

Do lifetime licenses carry forward to Next-Gen?

Yes they do. Annual maintenance will not be applied to free matching users that correspond to Classic lifetime user licenses. Unlike Classic where you received a long-term license key, with Next-Gen we Email you a new key each year.

Am I required to transition to Next-Gen?

You are not required to transition to the Next-Gen product. The fact that Classic is no longer being developed or supported does not mean that it will cease functioning. You may continue to use Classic for as long as it functions on your hardware and network platform.

Will DBA Classic run on modern Networks?

Many DBA Classic customers are on very old versions of the Pervasive database (2000i or V8) that may not function properly with the current Servers and PCs on the market (Windows 7, Windows 8, Server 2012, 64 Bit Machines, etc.). We have received reports from the field that DBA Classic will work in all of these environments, but will likely require an update of the Pervasive Database.

Download 30 Day Trial Version Pervasive Database »

Pervasive Upgrade Pricing »

Transition Resources:

Classic to Next-Gen Implementation Guide »

What does it cost to change to Next-Gen?

You are entitled to a free matching Next-Gen user for each Classic user license that you purchased from us. Therefore, there is no additional cost for software, unless you need to expand your user count. You should budget for a support subscription, which will be needed. Also be aware that you may need to upgrade your hardware and network to meet Next-Gen's system requirements.

System Requirements »

Is Next-Gen similar to Classic?

Next-Gen is a totally different product that originated from a software package we acquired in 2003. Next-Gen is programmed in Delphi (instead of TAS) and uses the Firebird SQL database (instead of Pervasive). Next-Gen and Classic offer similar modules, but the features and functionality within them are completely different.

How can I compare the two systems?

Next-Gen has an abundance of features that were never available in Classic. You can evaluate Next-Gen by downloading our free evaluation system, which includes a video library. For a listing of Classic features that are not available in Next-Gen, see chapter 2 in the Classic to Next-Generation Implementation Guide.

Download Free Evaluation System »

Can I transfer data from Classic to Next Gen?

Data transfer is accomplished by using the DBATRAN utility to export master tables from Classic into Excel spreadsheets, where they are edited and then imported into Next-Gen as specified by various tasks performed during the "Setup" phase of Next-Gen implementation.

Data transfer is not a "push button" process. Each master table is imported when called for within a specific implementation task, usually after prerequisite supporting tables are entered manually in advance.

Historical data cannot be transferred, nor can open orders or accounting balances. We recommend that you keep Classic on your network for historical reference purposes. Open orders and beginning account balances are entered manually just prior to system startup day, which is the day you cease using Classic and start operating exclusively in Next-Gen.

Why a spreadsheet transfer instead of direct import?

Master tables are exported into spreadsheets instead of being imported directly into Next-Gen. This is because most of the tables require some editing before they can be imported to make them compatible with the requirements of the corresponding tables in Next-Gen. Spreadsheets are optimized for editing large sets of data and are the ideal medium for data transfer purposes.

Data Transfer Downloads

Refer to the Classic to Next-Gen Implementation Guide for complete details on the data transfer process, which involves some or all of the following download files.

DBA2NG.EXE Installation Program for DBATRAN »

Pervasive 2000i SP4 »

Pervasive 2000i "Hot Fix" »

We purchased EVO-ERP. Can we still migrate to Next Gen?

Our company has no involvement with EVO-ERP or any knowledge of its data tables or technical specifications. Regardless whether you use EVO-ERP or any other add-on product, you are still entitled to a free matching Next-Gen user license for each Classic user license you purchased from our company. If you purchased EVO-ERP users without also purchasing users from us (which is not permitted by our license), those users do not qualify for free matching Next-Gen users.

How do I obtain my free matching users?

To get your free matching users, send an Email to accounting@dbasoftware.com and make your request. We will send you a license key by Email. We do not ship you a CD. Instead, you download the free single-user evaluation system from our website. The license key converts the free single-user system into a multi-user system.

Can I make the transition on my own?

Any company willing to put in time and effort and is committed to following the steps in the Implementation Planner can get Next-Gen up and running on its own, backed by our support. Be aware that this is a "transition" process, not a "conversion". You will be implementing a completely new system, which means that you must go through the exact same implementation process that any company would undergo coming from any non-DBA system.