Thanks for responding. They have told me that they have migrated the version of the database recently. The user is the same but maybe they forgot something... I've seen that the Catalog Owner in the connection is different than the user that connects.

If I write in the query a prefix with the table like "SELECT * FROM dbo.TABLE WHERE ..." then the Update Properties dialog works, but if I remove the prefix then fails. That didn't happen in the last version of the database, it worked without the prefix.

The trouble is that I'm working in an ERP with more than 7K datawindows and hundreds of tables, so I have to find another way than adding prefixes in the queries.

I've managed to save the datawindow and it seems to work properly, the datawindow updates the fields correctly. So I can continue working, but it would be interesting to guess what happens.

Could be that now the tables belong to an specific user and before was not the case?

Thanks!

Look at your Database Profile and ensure it has been set correctly on ALL of the tabpages.

In our case, for example, we have a named schema that hosts the PB Catalog tables:

Hi.

Is this anything related with permissions of the user I'm using to connect to the database? Maybe it needs access to system views to get the information of the tables?

Do you use different user than when you originally created the datawindow? If yes this user does have privileges to use that table? This table belongs to db owner or to a specific user? If it belongs to a specific user, then you may need to prefix table name with user (user1.proyecto). You SQL statement has any prefix in the from clause for that table?

Andreas.