Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Matlab - ODBC Driver Error: Driver unable to retrieve LENGTH for column number: 1

EcoStruxure Geo SCADA Expert Forum

Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Remote Operations
  • EcoStruxure Geo SCADA Expert Forum
  • Matlab - ODBC Driver Error: Driver unable to retrieve LENGTH for column number: 1
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
sbeadle
Kirk sbeadle Kirk
307
AndrewScott
Admiral AndrewScott
96
BevanWeiss
Spock BevanWeiss
90
AdamWoodlandToo
Lt. Commander AdamWoodlandToo
36
View All
Related Products
product field
Schneider Electric
EcoStruxure™ Geo SCADA Expert

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to EcoStruxure Geo SCADA Expert Forum
Solved
rcb.solar
Crewman rcb.solar Crewman
Crewman

Posted: ‎2024-10-04 11:07 AM

0 Likes
10
1028
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-04 11:07 AM

Matlab - ODBC Driver Error: Driver unable to retrieve LENGTH for column number: 1

Hello,

 

i'm using Matlab to query my Geo SCADA Database.

The same script was working in my previous environment, but since we have upgraded (Windows/Matlab/ClearSCADA), i'm no longer able to get data from the GeoSCADA Database.

 

Previous setup (OK): Windows Server 2008 / Matlab 2015b / Clear SCADA 2014
New setup (Not OK) : Windows Server 2019 / Matlab 2023a / Geo SCADA Expert 2019 81.8369.1 Update Dec 2022.
 
My script is able to connect to the DB with the database function :
DBconnexion=database(dbGS.ID,dbGS.user,dbGS.pwd);
(If i change a parameter i have an error from GeoSCADA)
 
The query has no issue executing with the select function (if i put something wrong in the query i have an error from GeoSCADA) :
dataAll=select(DBconnexion,sqlQueryAll);
 
But at the end on this select function i have the exception :
ODBC Driver Error: Driver unable to retrieve LENGTH for column number: 1
I think query is well executed, but the result can't be parsed.
 
 
It seems that i'm not the first one having this issue regarding this Matlab post : https://fr.mathworks.com/matlabcentral/answers/584702-unable-to-retrieve-data-from-a-clearscada-data...
Sadly there's no answer to this post 😞
 
 
Anyone that could help on this issue ?
thanks
 
 
Labels
  • Labels:
  • SCADA
  • Tags:
  • english
  • scada
  • SCADA app
  • SCADA software
  • SCADA tutorial
  • Telemetry and SCADA
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
AndrewScott
Admiral AndrewScott
Admiral

Posted: ‎2024-10-17 07:36 AM

0 Likes
0
760
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-17 07:36 AM

All versions of Geo SCADA support ODBC 1.0. No version of Geo SCADA supports ODBC 3.0.

Microsoft automatically map ODBC 3.0 onto ODBC 1.0, but this can't work for new features that are unique to ODBC 3.0 such as the SQL_DESC_OCTET_LENGTH column attribute.

 

I'm not familiar with JDBC, but there is no JDBC driver in Geo SCADA.

In addition to ODBC 1.0, Geo SCADA has an OLE-DB provider.

 

My only suggestions are to contact SE support to request a new feature or use to "Ideas" section of this forum to suggest a new feature. I expect adding support for ODBC 3.0 would be a significant development.


Andrew Scott, R&D Principal Technologist, AVEVA

See Answer In Context

Reply

Link copied. Please paste this link to share this article on your social media post.

Replies 10
AdamWoodlandToo
Lt. Commander AdamWoodlandToo
Lt. Commander

Posted: ‎2024-10-06 08:35 PM

0 Likes
1
993
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-06 08:35 PM

What query are you running? Perhaps knowing that could help us know where the problem might be, especially what column 1 refers to

 

I know in the past there have been some issues with very long strings in queries but given its Matlab I wouldn't have thought you would use strings much?

Reply

Link copied. Please paste this link to share this article on your social media post.

sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2024-10-07 12:56 AM

0 Likes
1
980
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-07 12:56 AM

You could activate ODBC Tracing (in the Windows ODBC setup tool), not sure if you use 32 or 64 bit, so you may need to try both. Hopefully the logs may help.

Reply

Link copied. Please paste this link to share this article on your social media post.

rcb.solar
Crewman rcb.solar Crewman
Crewman

Posted: ‎2024-10-07 06:37 AM

In response to AdamWoodlandToo
0 Likes
0
970
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-07 06:37 AM

Even if i try a very simple query i still have the error :

- Original Query :

SELECT TOP(1) "RecordId", "RecordTime" AS "~Time", "Id", "Value", "StateDesc", "Foreground", "Background", "Blink", "FileOffset" AS "_FileOffset" FROM CDBHISTORIC WHERE ("Id" IN (41401)) AND ("~Time" BETWEEN TIMESTAMP ''',datestr(date_start_sql-days(7),'yyyy-mm-dd HH:MM:SS'), ''' AND TIMESTAMP ''', datestr(date_start_sql,'yyyy-mm-dd HH:MM:SS'), ''') ORDER BY "~Time" DESC, "_FileOffset" DESC'
 
- Test Queries (with same error):
SELECT TOP(1) "Id" FROM CDBHISTORIC
SELECT TOP(1) "Value" FROM CDBHISTORIC
Reply

Link copied. Please paste this link to share this article on your social media post.

rcb.solar
Crewman rcb.solar Crewman
Crewman

Posted: ‎2024-10-07 06:45 AM

In response to sbeadle
0 Likes
0
970
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-07 06:45 AM

I have activated the ODBC Tracing, i find the following error from GeoSCADA :

DIAG [HY000] [Schneider Electric][Geo SCADA Expert database driver]Driver not capable (0) 
 
Complete log :
LangaData       4dc8-44d8 ENTER SQLExecDirectW 
HSTMT               0x0000026B0E0C75E0
WCHAR *             0x0000026B371CDD60 [      -3] "SELECT TOP(1)      "Id" FROM CDBHISTORIC\ 0"
SDWORD                    -3
 
LangaData       4dc8-44d8 EXIT  SQLExecDirectW  with return code 0 (SQL_SUCCESS)
HSTMT               0x0000026B0E0C75E0
WCHAR *             0x0000026B371CDD60 [      -3] "SELECT TOP(1)      "Id" FROM CDBHISTORIC\ 0"
SDWORD                    -3
 
LangaData       4dc8-44d8 ENTER SQLNumResultCols 
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC770
 
LangaData       4dc8-44d8 EXIT  SQLNumResultCols  with return code 0 (SQL_SUCCESS)
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC770 (1)
 
LangaData       4dc8-44d8 ENTER SQLNumResultCols 
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC700
 
LangaData       4dc8-44d8 EXIT  SQLNumResultCols  with return code 0 (SQL_SUCCESS)
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC700 (1)
 
LangaData       4dc8-44d8 ENTER SQLColAttribute 
SQLHSTMT            0x0000026B0E0C75E0
SQLSMALLINT                  1 
SQLSMALLINT                 18 <SQL_DESC_LABEL>
SQLPOINTER         0x000000E893FFC2C0
SQLSMALLINT               1024 
SQLSMALLINT *       0x0000000000000000
SQLPOINTER          0x0000000000000000 (NYI) 
 
LangaData       4dc8-44d8 EXIT  SQLColAttribute  with return code 0 (SQL_SUCCESS)
SQLHSTMT            0x0000026B0E0C75E0
SQLSMALLINT                  1 
SQLSMALLINT                 18 <SQL_DESC_LABEL>
SQLPOINTER         0x000000E893FFC2C0
SQLSMALLINT               1024 
SQLSMALLINT *       0x0000000000000000
SQLPOINTER          0x0000000000000000 (NYI) 
 
LangaData       4dc8-44d8 ENTER SQLNumResultCols 
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC770
 
LangaData       4dc8-44d8 EXIT  SQLNumResultCols  with return code 0 (SQL_SUCCESS)
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC770 (1)
 
LangaData       4dc8-44d8 ENTER SQLColAttribute 
SQLHSTMT            0x0000026B0E0C75E0
SQLSMALLINT                  1 
SQLSMALLINT                  2 <SQL_DESC_CONCISE_TYPE>
SQLPOINTER         0x0000000000000000
SQLSMALLINT                  0 
SQLSMALLINT *       0x0000000000000000
SQLPOINTER          0x000000E893FFC770
 
LangaData       4dc8-44d8 EXIT  SQLColAttribute  with return code 0 (SQL_SUCCESS)
SQLHSTMT            0x0000026B0E0C75E0
SQLSMALLINT                  1 
SQLSMALLINT                  2 <SQL_DESC_CONCISE_TYPE>
SQLPOINTER         0x0000000000000000
SQLSMALLINT                  0 
SQLSMALLINT *       0x0000000000000000
SQLPOINTER          0x000000E893FFC770 (4) <SQL_INTEGER>
 
LangaData       4dc8-44d8 ENTER SQLNumResultCols 
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC770
 
LangaData       4dc8-44d8 EXIT  SQLNumResultCols  with return code 0 (SQL_SUCCESS)
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC770 (1)
 
LangaData       4dc8-44d8 ENTER SQLNumResultCols 
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC6F0
 
LangaData       4dc8-44d8 EXIT  SQLNumResultCols  with return code 0 (SQL_SUCCESS)
HSTMT               0x0000026B0E0C75E0
SWORD *             0x000000E893FFC6F0 (1)
 
LangaData       4dc8-44d8 ENTER SQLColAttribute 
SQLHSTMT            0x0000026B0E0C75E0
SQLSMALLINT                  1 
SQLSMALLINT               1013 <SQL_DESC_OCTET_LENGTH>
SQLPOINTER         0x0000000000000000
SQLSMALLINT                  0 
SQLSMALLINT *       0x0000000000000000
SQLPOINTER          [Unknown attribute 1013]
 
LangaData       4dc8-44d8 EXIT  SQLColAttribute  with return code -1 (SQL_ERROR)
SQLHSTMT            0x0000026B0E0C75E0
SQLSMALLINT                  1 
SQLSMALLINT               1013 <SQL_DESC_OCTET_LENGTH>
SQLPOINTER         0x0000000000000000
SQLSMALLINT                  0 
SQLSMALLINT *       0x0000000000000000
SQLPOINTER          [Unknown attribute 1013]
 
DIAG [HY000] [Schneider Electric][Geo SCADA Expert database driver]Driver not capable (0) 
 
LangaData       4dc8-44d8 ENTER SQLDisconnect 
HDBC                0x0000026B0E0C9AF0
 
LangaData       4dc8-44d8 EXIT  SQLDisconnect  with return code 0 (SQL_SUCCESS)
HDBC                0x0000026B0E0C9AF0
 
 
Reply

Link copied. Please paste this link to share this article on your social media post.

rcb.solar
Crewman rcb.solar Crewman
Crewman

Posted: ‎2024-10-07 08:33 AM

0 Likes
0
963
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-07 08:33 AM

If i activate the ODBC driver log of GeoSCADA (HKEY_CURRENT_USER\SOFTWARE\Schneider Electric\ClearSCADA\DBOdbc\LogEnable = True) i have this :

 

07-OCT-2024 15:24:28.219 4C34 SQLAllocStmt( IN: Dbc 0000023614B75280)
07-OCT-2024 15:24:28.219 4C34 SQLAllocStmt( OUT: Stmt 0000023610824740, RetCode 0 )
07-OCT-2024 15:24:28.219 4C34 SQLSetStmtOption( IN: Stmt 0000023610824740, option 5 SQL_BIND_TYPE, value 0 )
07-OCT-2024 15:24:28.219 4C34 SQLSetStmtOption( OUT: RetCode 0 )
07-OCT-2024 15:24:28.224 4C34 SQLExecDirect( IN: Stmt 0000023610824740 )
07-OCT-2024 15:24:28.224 4C34 SQL: SELECT TOP(1) "Id" FROM CDBHISTORIC
07-OCT-2024 15:24:28.224 4C34 SQLExecDirect( OUT: RetCode 0 )
07-OCT-2024 15:24:28.224 4C34 SQLNumResultCols( IN: Stmt 0000023610824740 )
07-OCT-2024 15:24:28.224 4C34 SQLNumResultCols( OUT: col_count 1, RetCode 0 )
07-OCT-2024 15:24:28.229 4C34 SQLNumResultCols( IN: Stmt 0000023610824740 )
07-OCT-2024 15:24:28.229 4C34 SQLNumResultCols( OUT: col_count 1, RetCode 0 )
07-OCT-2024 15:24:28.229 4C34 SQLColAttributes( IN: Stmt 0000023610824740, index 1, type 18 SQL_COLUMN_LABEL, value 000002366C801D90, max_len 2048, actual_len 0000007D07FFC0D4, integer 0000000000000000 )
07-OCT-2024 15:24:28.229 4C34 SQLColAttributes( OUT: RetCode 0, Value Id, ActualLen 4 )
07-OCT-2024 15:24:28.229 4C34 SQLNumResultCols( IN: Stmt 0000023610824740 )
07-OCT-2024 15:24:28.229 4C34 SQLNumResultCols( OUT: col_count 1, RetCode 0 )
07-OCT-2024 15:24:28.229 4C34 SQLColAttributes( IN: Stmt 0000023610824740, index 1, type 2 SQL_COLUMN_TYPE, value 0000000000000000, max_len 0, actual_len 0000007D07FFC564, integer 0000007D07FFC670 )
07-OCT-2024 15:24:28.229 4C34 SQLColAttributes( OUT: RetCode 0, Value 4, ActualLen 0 )
07-OCT-2024 15:24:28.259 4C34 SQLNumResultCols( IN: Stmt 0000023610824740 )
07-OCT-2024 15:24:28.259 4C34 SQLNumResultCols( OUT: col_count 1, RetCode 0 )
07-OCT-2024 15:24:28.259 4C34 SQLNumResultCols( IN: Stmt 0000023610824740 )
07-OCT-2024 15:24:28.259 4C34 SQLNumResultCols( OUT: col_count 1, RetCode 0 )
07-OCT-2024 15:24:28.259 4C34 SQLColAttributes( IN: Stmt 0000023610824740, index 1, type 1013 ??, value 0000000000000000, max_len 0, actual_len 0000007D07FFC444, integer 0000007D07FFC4F8 )
07-OCT-2024 15:24:28.259 4C34 SQLColAttributes( OUT: RetCode -1, Value 0, ActualLen 0 )

 

Still this "type 1013" error when treating the result

Reply

Link copied. Please paste this link to share this article on your social media post.

AndrewScott
Admiral AndrewScott
Admiral

Posted: ‎2024-10-07 12:16 PM

0 Likes
1
931
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-07 12:16 PM

The Geo SCADA ODBC driver doesn't support the SQLColAttributes() method with attribute 1013, hence it returns a "Driver not capable" error response. I cannot find any documentation on attribute 1013. It isn't a standard attribute defined by Microsoft. Attributes above 1000 are defined as "driver specific", so I can only assume this is something specific to Matlab but that doesn't explain why it would be requesting this attribute from Geo SCADA and not handling the unsupported error response.


Andrew Scott, R&D Principal Technologist, AVEVA
Reply

Link copied. Please paste this link to share this article on your social media post.

rcb.solar
Crewman rcb.solar Crewman
Crewman

Posted: ‎2024-10-10 07:57 AM

In response to AndrewScott
0 Likes
0
885
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-10 07:57 AM

Hi Andrew,

thanks for your answer, i have opened a support case on Matlab, here is their answer :

 

The attribute number 1013 is defined by Microsoft. You can find its definition in Microsoft's ODBC specification on the page linked below.
https://github.com/microsoft/ODBC-Specification/blob/master/Windows/inc/sql.h

As suggested in the file above, SQL_DESC_OCTECT_LENGTH is defined as the value 1013. The definition of SQL_DESC_OCTET_LENGTH can be found here:
https://learn.microsoft.com/en-us/sql/odbc/reference/syntax/sqlcolattribute-function?view=sql-server...

MATLAB refers to the name SQL_DESC_OCTECT_LENGTH provided by Microsoft instead of the hardcoded value 1013, and the name SQL_DESC_OCTECT_LENGTH is interpreted as that number due to the definitions in Microsoft's ODBC specification. We need this information to know how much memory to allocate when reading from a column.

We noticed that several things were updated with the setup on your end before the error occurred, including MATLAB releases and SCADA versions. I have confirmed with my colleague in the development team that the attribute SQL_DESC_OCTECT_LENGTH was used in the older release as well. Hence, it is possible that the update from Clear SCADA to Geo SCADA could be the source of the incompatibility you are encountering. 

Reply

Link copied. Please paste this link to share this article on your social media post.

AndrewScott
Admiral AndrewScott
Admiral

Posted: ‎2024-10-10 08:40 AM

0 Likes
1
881
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-10 08:40 AM

The Geo SCADA ODBC driver only supports ODBC 1.0 and therefore only supports the ODBC 1.0 column attributes for the SQLColAttributes() method. These are defined by Microsoft here (see SQL_COLUMN_xxxx starting on line 679):

https://github.com/microsoft/ODBC-Specification/blob/master/Windows/inc/sqlext.h 

 

SQL_DESC_OCTET_LENGTH (1013) is an ODBC 3.0 column attribute, so is not supported by any version of Geo SCADA. The closest supported attribute is SQL_COLUMN_LENGTH.

 

If MATLAB now only supports ODBC 3.0 then it will not interoperate with Geo SCADA which only supports ODBC 1.0. Did older versions of MATLAB support ODBC 1.0, thus allowing interoperability?

 


Andrew Scott, R&D Principal Technologist, AVEVA
Reply

Link copied. Please paste this link to share this article on your social media post.

rcb.solar
Crewman rcb.solar Crewman
Crewman

Posted: ‎2024-10-17 05:21 AM

In response to AndrewScott
0 Likes
0
769
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-17 05:21 AM

Older versions of Matlab was using a JDBC-ODBC bridge, that's the assumption of Matlab support, but this bridge is now deprecated by Oracle and not used in new version of Matlab.

Is this ODBC 1.0 limitation in GeoSCADA only apply to GeoSCADA 2019 that i use ? I mean, is ODBC 3.0 compatible with a more recent version like GeoSCADA 2023 ?

Is there another way to connect to GeoSCADA DB, for example in JDBC ?

thanks,

Renaud

Reply

Link copied. Please paste this link to share this article on your social media post.

AndrewScott
Admiral AndrewScott
Admiral

Posted: ‎2024-10-17 07:36 AM

0 Likes
0
761
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-10-17 07:36 AM

All versions of Geo SCADA support ODBC 1.0. No version of Geo SCADA supports ODBC 3.0.

Microsoft automatically map ODBC 3.0 onto ODBC 1.0, but this can't work for new features that are unique to ODBC 3.0 such as the SQL_DESC_OCTET_LENGTH column attribute.

 

I'm not familiar with JDBC, but there is no JDBC driver in Geo SCADA.

In addition to ODBC 1.0, Geo SCADA has an OLE-DB provider.

 

My only suggestions are to contact SE support to request a new feature or use to "Ideas" section of this forum to suggest a new feature. I expect adding support for ODBC 3.0 would be a significant development.


Andrew Scott, R&D Principal Technologist, AVEVA
Reply

Link copied. Please paste this link to share this article on your social media post.

Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of