Due to some changes in newer versions of CYMA (CYMA 15+), Acctivate for CYMA users have reported some conflicts in how Acctivate connects with CYMA and how CYMA reports are configured.
Starting in Acctivate 10.2sp1, Acctivate now creates a Pervasive.SQL Database named AcctivateCYMA[CompanyID] which uses our custom database definition files (DDFs) in the CYMA4\Acctivate directory. Previously, Acctivate used to name the database CYMA[CompanyID].
All access to the CYMA data is done through that database name. While ODBC is used to connect to the Pervasive.SQL database, ODBC DSNs are no longer used. All connections are DSN-less, so no DSNs need to be set up in the either the 32-bit or 64-bit ODBCAD32 utility, and any DSNs that are already there from previous versions of Acctivate will no longer be used.
Acctivate connects to CYMA data in two ways, via a direct connection to the Pervasive.SQL database, and through a Microsoft SQL Server linked remote database connection. Acctivate’s direct connection uses the “Pervasive ODBC Client Interface” driver, and the linked connection between Microsoft SQL Server and Pervasive.SQL uses the “Pervasive ODBC Interface” driver if MSSQL is 64-bit; “Pervasive ODBC Client Interface” if MSSQL is 32-bit.
There’s also the AcctivateCYMA2[CompanyID] DB in Pervasive.SQL, but it’s rarely-used. It contains CYMA custom field definitions, and I think Acctivate only uses it to get the custom fields on the Customer Information window. There’s no MSSQL link for that; Acctivate accesses it directly.