
The following table shows how the operating system architecture affects the choice of tier.Ĭonsider adding the server keyword to the declaration of the Main method.Īnnouncements: New book: "Inside Microsoft Dynamics AX 2012 R3" now available. The preceding code example can run on either the client tier or the server tier.
#THIN SQL CLIENT ODBC 64 BIT#
Always get fields in numerical order, such as 1 then 2 the 3 etc.Įrror("Failed to log on to the database through ODBC.") ģ2 Bit and 64 Bit Windows Operating System It is a server/client based architecture in which the ODBC server component must be installed on the historian machine itself and the ODBC client installed on any machine wishing to make queries. It is not possible to get field 3 and then 1. The Canary Historian ODBC is used for generating reports using SQL queries and populating data from the Enterprise Historian into SQL databases. then loop through each row in the result. Statement = odbcConnection.createStatement() Perm = new SqlStatementExecutePermission(sql) Assert permission for executing the sql string. Sql = "SELECT * FROM MYTABLE WHERE FIELD = " OdbcConnection = new OdbcConnection(loginProperty)
#THIN SQL CLIENT ODBC DRIVER#
and of course the ODA driver won’t work without a fat client install. We don’t want to fire up the Oracle ODBC connection as this will compromise security etc. Create a connection to external database. I need to access the one world data base for ad-hoc queries from a thin client, the client machine has no oracle client and no one world. The code example assumes that you have already created the DSN in Windows. The following X++ code example uses ODBC to connect to an external database.


Ongoing maintenance is simpler if the DSN is created on the AOS tier.
