Link to an ODBC Table created using the Microsoft Access Text Driver

[Anonymous user]

I am trying to link an ODBC Table to Geo SCADA using the Server Configuration Tool, but I am having issues using the correct connection string for the Microsoft Access Text Driver. (This is to import a .csv into Geo SCADA).

I have tried multiple connection strings without any luck. This is the latest format I used:

Driver=Microsoft Access Text Driver (*.txt, *.csv);Dbq=c:\txtFilesFolder\; Extensions=asc,csv,tab,txt;

What is the correct format for the connection string for this particular ODBC driver?

[BevanWeiss]

Is there a reason that you can't just use the ODBC Driver?

As has been raised several times in the past week on the forum here, you will be setting yourself up for terrible ClearSCADA / GeoSCADA Expert performance if you use a Linked ODBC Table in your Logic.

I think this link suggests you will need to jump through a bunch more hoops to use the Access Driver

https://docs.microsoft.com/en-us/office/troubleshoot/access/cannot-use-odbc-or-oledb

Perhaps the plain Microsoft ODBC Text Driver would work better?

https://docs.microsoft.com/en-us/sql/odbc/microsoft/text-file-driver-programming-considerations?view...

[sbeadle · Accepted solution]

For clarification (because the 'ODBC Driver' can mean 3 things!

a) The ability to connect an ODBC client application (like Excel, VB, ...) to read and write data

b) The ability to link external database tables within the Geo SCADA database so that client displays and (warning) Logic can read/write from those external tables

c) The ability to read data from an external table and bring it in as point values/times/quality. (As if it was a device). 

This latter facility is what you might consider. No 'danger' of locking the database. Search the Help for 'odbc driver guide Introduction to the ODBC Driver'

[Anonymous user]

Thank you!

I have set up a system DSN using the 32-bit Microsoft Text Driver (Instead of using the 64-bit Microsoft Access Text Driver), as suggested by Bevan, which has been detected by the ODBC Connection object within Geo SCADA.

Now I just need to use the ODBC Query and respective ODBC Data Points to extract the data from the DSN, following the steps highlighted in the Help topic that Stephen recommended.