When we started the ERP projects our main goal was to publish the alpha360 data models; the WX projects where just "limited core" projects to help developers better understand the data models. Things have changed a lot since the early days of the projects and - especially with v2 - they are now more complete; more developers are using them to develop their own solutions. So what is the best way to "follow up" with NEWER versions and "include" new features of the projects in YOUR solutions? Starting with version 2 releases, all projects, have now a reference version ; this is always the first, non beta release [with the exception of the Retail project] - release 2.07 is the reference version for all projects. All our additions and changes are done with reference to version 2.07 and the details are included inside the projects. So a simple search, say for 2.08, is sufficient to find all changes and additions we have done in v2.08. There are also some great features in the WX IDE; you can Search for last changes, compare projects etc. Just note that you should also use some kind of notation in YOUR projects to "label" YOUR changes or additions. A good practice would also be to create YOUR own windows or reports, instead of doing extended changes to ours and of course label them accordingly. We can also include YOUR code/changes directly in newer versions, if we think they are of GENERAL INTEREST; but note that they will be available to all licensees. The above does not affect in-house developers with a consultancy contract - their changes and additions are always kept synchronized by our developers.

Table Names In the alpha360 data models, tables or data files, are of one of the following types: Dimension table Transaction table Sum table Although it might seem "strange", most of the tables in the data models, are Dimension tables - gParty, sSalesArea, bBusinessDocument etc are all Dimension tables. The only reason they exist is because we need them to post to transactions, to help us with grouping, reporting and statistics and "maybe" for audit reasons ... Our financial data is included in the transaction tables and "sum values" for financial data are included in the "sum tables". Sum tables just help us "do things like reporting faster" AND can be reconstructed - at any time - from the data in the transaction tables !! All transaction and sum tables - except those that are used in Accounting - start with a "t". Additionally sum tables end with a "_sum". The transactions in Accounting are named aAccountingTransaction and the sums are named aAccountingFY_sum (Fiscal Year Sums) and aAccountingRP_sum (Fiscal Period Sums). Now all other tables - of type dimension - start with a letter that "tries to show" where they are used. Everything that starts with a "g" means that the table is probably used in many functional areas - like "gParty". Here is a short list: "a": for Accounting "b": for Business Documents "c": for CRM "r": for Restaurant "j": for POS "h": for HRM "s": for Sales "p": for Purchases "f": for Public Sector Accounting "x": for Access Control Field Names String fields start with the lower case letter " s " Memo fields start with the lower case letter " m " Integer fields start with the lower case letter " n " Real fields start with the lower case letters " nr " Decimal fields start with the lower case letters " nd " Currency fields start with the lower case letter " c " Date fields start with the lower case letter " d " DateTime fields start with the lower case letters " dt " Time fields start with the lower case letters " d " Boolean fields start with the lower case letter " b " ​ Primary keys end with  _PK and Foreign keys end with  _FK . take a look here for more information: https://www.alpha360.biz/universal-data-model

If you are having difficulties accessing your downloads or you have "misplaced" your license info send us an email and we will fix it !! Due to possible time differences, just give us 1 working day ...