At 10:10 AM 7/27/2001 -0400, Karen Tellef wrote:
>I just found an unexpected result when adding a new column
>to a table! Verified in DOS 6.5+ 1.839xRT03 and in
>Windows 6.5++ 1.842xRT03.
>
>I had a table called PAYMENTS with a column STATUS that has
>a default defined to 'OK'. In many cases after inserting a
>row, the user will take out the word 'OK' to leave the column
>null.
>
>I had to add a column to the table and found out to my client's
>chagrin that all the rows that had a null STATUS now had the
>default 'OK' put in! We had to go to last night's backup and
>match up rows to set them back to null. I tested here at my
>office with both the versions mentioned and yes it happens.
>Adding a column to a table will cause default values to be
>inserted into null columns.
Karen,
I'm very pleased to inform you that the "long time bug" as
mentioned above, have been FIXED in the upcoming in-line
path-1 of The Glorious R:BASE 2000 (ver 6.5++) for Windows,
to be released shortly.
Also, thanks for reporting that very old bug on R:DCC and
helping our talented and dedicated R:Team to bring the BEST
of R:BASE!
Very Best Regards,
Razzak.
===================================-============================
R:BASE Developers's Conference: http://www.rbase.com/conference
Official R:BASE List Server: mailto:[EMAIL PROTECTED]
RBTI Events/Training: http://www.rbase2000.com/events
R:DCC Members: http://www.rbase2000.com/rdcc
================================================================
R:BASE, Oterro & R:Tango are registered trademarks of RBTI.
==================================-=============================
