Highlights of AdaptAccounts for SQL Server 2012


AdaptAccounts for SQL Server 2012 runs on SQL Server 2012 and SQL Server 2008.

AdaptAccounts for SQL Server 2012 improves reliability and performance with minimal or no impact on user modifications to recent AdaptAccounts for SQL Server versions. This enables easy upgrades to the newest version. Users of AdaptAccounts for SQL Server 2008, AdaptAccounts for SQL Server 2005 and AdaptAccounts for SQL Server 2001 can migrate from those versions with minimal or no changes to any customizations at the application task level. The reason this works is that changes have been at the system level and would not typically affect application tasks.

Of equal importance is the ongoing focus on the use of AdaptAccounts for SQL Server as an accounting database engine with multiple client interfaces. At present the standard user interface is the Win32 Delphi 7. Other interfaces being implemented by other developers are anticipated to be available at a future date.

AdaptAccounts for SQL Server 2012

ArTransDate determines GlTransDate in Accounts Receivable

ApTransDate determines GlTransDate in Accounts Payable

The use of a separate GlTransDate that may be different from the ArTransDate of a transaction within Accounts Receivable has been discontinued. Similarly, the use of a separate GlTransDate that may be different from the ApTransDate of a transaction within Accounts Payable has been discontinued.

This approach reverts back to that used in all AdaptAccounts versions prior to AdaptAccounts 2001 for SQL Server 2000. The GlTransDate for a Journal Entry originating from Accounts Receivable is the same as the ArTransDate of the transactions summarized by that Journal Entry. Similarly, the GlTransDate for a Journal Entry originating from Accounts Payable is the same as the ApTransDate of the transactions summarized by that Journal Entry.

The new schema drops all occurrences of GlTransDate and associated database objects in Accounts Receivable and Accounts Payable. Applicable stored procedures and triggers have been changed to reflect this. This also eliminates the need for user maintenance of the Earliest/Latest Open ArTransDate/ApTransDate since only the Earliest/Latest Open GlTransDate needs to be maintained.

FiscalPeriodDate table

This new table provides improved performance in determining the applicable fiscal year and period for a date. It also provides a convenient way to ensure that direct user editing of the FiscalPeriod table has not left any gaps.

New Help system (HTML Help .chm)

The new Help system is implemented as HTML Help (Adapta2012ms.chm). It has been extensively updated to improve usability.

Client-independent stored procedure arguments

Stored procedures with configuration information provided by the client as arguments to the stored procedure have been changed to remove those arguments. The new methods do not require the client to know and pass those arguments. This facilitates multi-client development.

AdaptAccounts for SQL Server 2008

Schema Domain definitions (user-defined data types) replaced by directly specified data types

Schema Domain definitions (user-defined data types) have been replaced by directly specified data types. For example, the columns defined using the AadAccount domain reference (user-defined data type) that indirectly specified the data type of varchar(40) are now specified directly as varchar(40). This makes database programming easier since some objects did not recognize these user-defined data types and the developer needed to keep the domain definitions handy so that the data type could be specified directly. This also facilitates the use of other database programming tools that do not directly support user-defined data types.

GlBalance table automatically synchronized with FiscalPeriod table

Previous versions required user maintenance of GlBalance control information to change available fiscal years in the GlBalance table. This is no longer required. The system automatically synchronizes the GlBalance table to include all fiscal years in the FiscalPeriod table whenever the FiscalPeriod table is changed.  

Primary Company database includes User and Company login tables previously in separate database

Previous versions user a separate database to maintain the User and Company login tables. These tables are now maintained in the primary company database e.g. Adapta2008msCo1. This means a minimal configuration is one database which can also simplify programming tool requirements.

FiscalPeriod table control information dropped from AaCompany table

Previous versions maintained FiscalPeriod table control information within the AaCompany table. This information is now directly obtained from the FiscalPeriod table.  

Other AaCompany table changes

Other changes simplify the AaCompany table.
Accounts Receivable and Accounts Payable aging specifications now occur directly in the aging stored procedures.
The "..Strict" entry specification fields e.g. IsAccountArEntryStrict have been dropped.
The "..IsPreFilter" specification fields e.g. AccountIsPreFilter have been dropped.
Some column names have been changed to improve their self-documenting and better reflect their role. For example, AccountSegmentSIDMax is now AccountSegmentIndexMax and AccountSegmentSIDFinancial is now AccountSegmentIndexFinancial.

August 2012