For a long time I use the odbc link to connect Dataease a sql Database. In a table of sql database a field as been added.

In dataease I delete dbo form changed, so with database link I rebuild the table after reffresh. The new field it appear, but

the data does not: the table is empty.

Please help me.

Most likely the problem is that the new column type is not supported by the DataEase ODBC driver resulting in an "illegal" SQL sent to the driver.

After many hours of tests I found a "solution" or rather a trick to work. 

In SQL environment I renamed the table with various problems in DataEase eg: "ARTICOLI" Iin "ARTICOLISOS".

In DataEase I deleted "ARTICOLI.dbo" and I created the link with "ARTICOLISOS". At this point the new dbo Table is fully functional. 

I'm back in the SQL environment and I renamed the "ARTICOLISOS" table with the original name "ARTICOLI". 

So in DataEase I deleted "ARTICOLISOS.dbo" and after a refresh I created the new form with the SQL table "ARTICOLI.dbo" ,  finally everything works. 

I think the problem is in updating the ODBC links.

Nothing is more satisfying than when one figure a problem like this out ;-)

I think you are most likely right.

The ODBC implementation is very old as Microsoft has abandoned it.

We all do mistakes and so do Microsoft. The only cross database solution that was close to working was ODBC but they abandoned it and went down other routes which they have abandoned too in short order.

The biggest problem now is the x32/x64 barrier between ODBC drivers where the majority of software is x32 running on x64 when the new drivers are x64 etc.

It should be easy but it never was.

The problem here is most likely that our end of the ODBC link is not talking to the updated end of your ODBC link because some key tables has changed name or format etc.