"Database" Object it's not available on MTP1000... why ?

Stefan Arcularius

Hi Bert,

I am wondering what 'SQLLAKLIJNDEVION' is used for in your connection string. If you are specifying a server IP address, it should just be an IP address, nothing more.

Of course, if the default port is not used, you need to add it.

In addition, your Panel must be able to reach this IP address. This will be the case either if the Panel is on the same subnet or, if on a different subnet, if a router is configured and working.

I did some tests where I configured the sever with its IP address and a router to reach this address from the Panel's interface. My connection string was:

const connectionString = "DRIVER={ODBC Driver 17 for SQL Server}; DATABASE=testDatabase; UID=test; PWD=test; trusted_connection=no; SERVER=192.168.123.1;";

Kind regards
Stefan

 I tried to make it work on a MTP1000 but as I went to compile, it prompts an error:

,Object Member no válido: Database en fila 10, en columna 30,,,9:31:11

it seems like "Database" Object it's not available on MTP1000... why ?

------------------------------------------------------------------------------------------
Split from SQL connection from Unified panel.

Hi, I attached a photo from HMI...

I've tried to make a global function to do the select statement but it's impossible to import....

also I tried to do directly from snipped code... neither it works :-( ,it prompts that Database object doesn't exist...

link to tia portal test file:

[snip]

CODE:

export async function sqlSelect(textFieldName) {


let textElement = UI.ActiveScreen.FindItem(textFieldName);
textElement.ProcessValue = "Started function";
try {
textElement.ProcessValue = "Started try ";
const connectionString = "DRIVER={ODBC Driver 17 for SQL Server}; DATABASE=tia; UID=hmi; PWD=941246900; trusted_connection=no; SERVER=192.168.0.254;";
//let connectionString = "Driver={SQL Server}; Server=localhost; Database=MyDB;trusted_connection=yes;";

let conn = await HMIRuntime.Database.CreateConnection(connectionString);
textElement.ProcessValue = "Conn done";
//let query = "Select * from MyTable;";
// ud_pedido is PK auto_increment INTeger ~ descripcion is an String with the description of the unit_id ( in spanish )
// for test purposes I only want to get only ONE String data, to populate ONE text field as test
let query = "Select descripcion from dbo.test ORDER BY ud_pedido  OFFSET 1 ROWS FETCH NEXT 1 ROWS ONLY;";
textElement.ProcessValue = "Select statement recorded";
// above code works well in SQL throwing 1 string..

let results = await conn.Execute(query);
textElement.ProcessValue = "query executed";
if (results !== undefined && results !== null) {
let statements = results.Results;
textElement.ProcessValue = "Results obtained";
for (let statement in statements) {
let rows = statements[statement].Rows;
for (let i in rows) {
let row = rows[i];
for (let key in row) {
// original behaviour
HMIRuntime.Trace(key + ":" + row[key]);
// modified behaviour to set the Text Element with data from SQL..
// wroten all the times in the loop
// ( but in example only 1 cause select returns 1 row with 1 item)
let t = (key + ":" + row[key]);
textElement.ProcessValue = t;
}
}
}
}
conn.Close();
} //try end

catch (e) {
//write only a error state on text field
let t = ('SQL error undefined');
textElement.ProcessValue = t;

let res = e.Results;
for (let statement in res) {
let errors = res[statement].Errors;
for (let i in errors) {
let detailed = errors[i];
HMIRuntime.Trace("Errors state : " + detailed.State);
HMIRuntime.Trace("Errors Message : " + detailed.Message);
}
}
} // catch end
return 0


}

Yes it compiles with no erros, but it's impossible to use the function inside "GM"

I also did a simple Global Module, with one unique sync function , without parameters, returning "hello World" and also i got the same error:

"ReferenceError: cannot instantiate module 'XXXXX'

How can do that?

I'm really stuck

thanks for  your support, maybe I need to re-install all the software.

now i'm working with TIA18 and my company has bought the upgrade to V19, it's time to do now!

thanks