Thanks, Karen - that looks like my third column... I guess I'll do them all the same and see what happens.
This is something that I do every year (bit late this year) but it must(!) have been alright lat January. Regards, Alastair. ----- Original Message ----- From: [email protected] To: RBASE-L Mailing List Sent: Wednesday, January 28, 2009 4:09 PM Subject: [RBASE-L] - Re: ERROR- Specified default value is not valid for column Relea... Yeah, this is real familiar to me! Way back in Nov 2007 I reported this as a "bug". I did an unload and a load to fix a corrupted database and it hung on a default .#DATE column with the exact message you got. RBTI did not change this behavior: "Solution Provided (not a bug)". I can't remember what they told me to do -- I think I had to change it to a computed column rather than a default?? Karen I'm reloading a table and I guess this is a tightening up that I have missed. The column is (not surprisingly) a DATE column and the default is : (.#DATE) I've tried un-dotted and without brackets but still get the error. Stranger, I have two other similar columns, Entry_Date &Up_Date, one of which has the same default but the other is computed rather than defaulted and uses an Expression with the calculation: (.#DATE). Both these columns follow the ReleaseDate in the table so I don't know (yet) if either will fail also. Any thoughts, anybody? Regards, Alastair ------------------------------------------------------------------------------ No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.176 / Virus Database: 270.10.15/1921 - Release Date: 28/01/2009 06:37
