Best practices: I have 2 Tables and these have different structures depending on the software version

Hello,
I bought TMS Aurelius and now trying to get ahead, but fail because of a simple requirement.
The following constellation: Our database has different structures / data types for one and the same table, depending on the version. That means, in version 1 e.g. the column date = string, in version 2 = date.
My standard SQL statement (for Version 2) looks like this:

FD_Qry.SQL.AddStrings( [
'SELECT',
'NZ.Datum,',
'LTRIM(CA.PERSNR) "Pers.-Nr.",',
'CA.NAME,',
'CA.VORNAME,',
'NZ.Wert1,',
'NZ.Wert2',
'FROM KTORECHLISTEWERTE AS NZ',
'LEFT JOIN PERSONALSTAMM AS CA ON NZ.CA_ID = CA.IDENTIFIKATION',
'WHERE',
'NZ.LISTENNR = ' + QuotedStr( '111' ),
'AND NZ.Datum between GetDate()-100 and GetDate()-1',
'ORDER BY 3, 4, 2, 1'
] );

==============================
My questions:

  1. How do I have to proceed? Since the table structure / data types can be different for each customer, I probably cannot use the Data Modeler.

  2. How do I have to create the classes if the data types and number of columns per table are different in the different versions?

  3. How do I have to implement this simple requirement so that I can display the data in a DBGrid.

Many Thanks!

I believe your option would be to use dynamic properties:
https://download.tmssoftware.com/business/aurelius/doc/web/dynamic_properties.html

Great, that looks good!

Many Thanks!

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.