Hello,

Has anyone come across any problems with TCL SQL UPDATE? I just have.

At TCL I tried:

SQL UPDATE table SET date=01/11/2004" WHERE date=01/12/2004"

This did not do all corrections and in fact mucked up the table as the ones it missed can no longer be changed in the editor and if I try editing AB123X the changes are actually written to AB123 ! believe it or not. I noticed that the dict key length was 5 so made it 6 then restored the table and tried the SQL UPDATE again and it worked.

Can anyone confirm that this is a problem? Could it be a Universal driver issue?

Thanks

Phil

It sounds as though by doing an SQL statement you have applied PROTECT.MFS to the table which enforces domain validation so that if the column were defined as CHAR(5) it would TRUNCATE anything longer than 5. So in a sense this is expected behaviour although not expected by us who are used to variable length columns.

Dim and distant memory serves that you can set the protection level to dictate default behaviour, truncate or abort with warning.

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

Im not sure how to set the protection level.

View this thread on the forum...