Thank you for your help, i resolve the problem with your comments.

On version 8 i used this:

SQLCA.Database = "BASEPRUEBA" 

but on version 2019 , i have to change for this:

SQLCA.DBParm = "Database='BASEPRUEBA' Provider='SQLNCLI' "

sysdatabases is a view in the master database with an owner id of sys.

Make the change already suggested, fully qualify the select:

SELECT ... FROM master.sys.sysdatabases

Hi Rafael;

    In SQL Server, the table should be "Sys.Databases". For example ...

SELECT name, user_access_desc, is_read_only, state_desc, recovery_model_desc  
FROM sys.databases;

    Make sure that the table name is spelled correctly with the period (.) in the name.

HTH

Regards ... Chris

Hi Rafael,

General note migrating any PRE PB 10 ==> PB 10+

Starting at PB 10, PowerBuilder moved from ANSI strings to Unicode UTF-16LE. So all strings are now 2 byte characters. Every access to external resources like databases and external function calls to DLLs is impacted.

RE: sysdatabases

Until you know what is actually failing it is hard give direction. Hence, ==>

Could you try just for experiment to prefix sysdatabases with its owner and/or database?
The fully qualified name should work no matter what may be your current database and/or current default schema.

SELECT . . . FROM master.sys.sysdatabases;

HTH /Michael

I connect to SQL 2008 with sqlncli as provider and with SQL 2014 with sqlncli11 as provider, in database painter i can see all the tables and the data, in dw painter i can see the data without the error

I review the parameters in the database painter and the app and are the same. But in the app i have the error when i try to retrieve data in the datawindow

Hi, Rafael -

What version of SQL Server are you using? What are the transaction object (SQLCA) property values (SQLCA.DBMS, etc.)? Can you retrieve data for this DataWindow Object in the DW Painter without the error? If so, what are the differences in the DB Profile you are using from the PB IDE and what the app is using during execution?

Also, I believe Microsoft is going to or may already have deprecated several old system tables in the "master" database.  Perhaps the newer Native Client interfaces disallow their use? Even though older constructs like sysdatabases may be visible, access rights may have changed. you should refactor your SQL SELECT statements to use the newer, recommended INFORMATION_SCHEMA views if your version of SQL Server supports them.