Blue chip professional skills from an independent

Database

CODA stores its data in a standard SQL database, frequently Microsoft SQL*Server or Oracle depending on the details of the installation.


Given this, and the way in which CODA chooses to store its data (see below) there are many possibilities of writing targeted data extraction scripts to add further value to your CODA system.


Though the relationship between the tables in the database is not always obvious, CODA provides excellent reference information on all the actual fields in the database. Further, all the field names are generally human/readable/understandable, and little information is stored in coded format - again it is mostly stored in a format that can be easily understood.


For these reasons, it is very possible to extract data directly from the database in a useful form without resorting to one of the CODA APIs, such as XMLi or web services. This can be useful since these methods generally require extra licence payments.


How can we help?


We have many years experience of working with the CODA database, and can assist in extracting data for all the complex data structures that CODA holds. For example:

  • invoices together with information on part payments, and tax together with customer and supplier details;
  • customer and supplier details;
  • balance information, e.g. for running credit checks.

Note that this is not a substitute for a report writing tool. Where it is very, very useful is when you have a need to extract limited amounts of data. One example would be where you have an operational system that needs to know when invoices have been paid, and whether in part or in full. It is easy to write an overnight batch extraction process that produces the information in machine readable format for the operational system to use.


Writing to the CODA database


The CODA database has some tables that may be written to by third parties (such as the link tables).


In general, never write any data to the database unless you are certain of the outcome. You risk corrupting your installation, and needing to restore from backup.


CODA employs checksums on various of its tables, that only the product can correctly update. If during usage, the product recognises that a checksum does not equal the expected value, it will prevent access to the data. The only way to free this up is to correct the checksum; the only people who can do that are CODA, by issuing a new checksum key. This is done via the CODA helpdesk.