Reading ODBC Signals in the Correct Format

[abdullah123456789]

Hello, I'm having trouble with the ODBC connection in the November 2024 version of Geo Scada Expert 2023. I created a Data Source for ODBC, which allows me to import data from an SQL database into Scada. I'm using the Column Match Lookup method for this. Integrating data into Scada using rows and columns doesn't work for me.

However, there's a problem here. The value in the column I'm looking up in SQL isn't a numeric value, so I have to select String Point, not Analog Point. When I select String Point, I only get results if the desired value isn't a decimal value, but an integer.

To fix this, when I adjust the Format section of the String Point tab of the signal, I get an "Invalid Format" error as shown in the image, no matter what I select.

I need to somehow integrate decimal expressions from the SQL database into Scada using ODBC. Can you help me with this?

[AndrewScott]

The only value formatting that is supported for string points is case conversion (uppercase or lowercase) , see Text String Syntax. You can't apply numeric formatting to something that isn't a number.

If the SQL database is storing the value as text (a string) then it can only be copied 'as is' into a string point.

If the text value is made up from a sequence of digits/decimal point that you want to interpret as a number then you may be able to cast or convert the value in the SQL query. For example, in Microsoft SQL Server you can use CAST(MyField AS real). The resulting numeric value can then be stored in a analog point.