But it doesn't allow you to control the values when other changes occur in that record if you are using it for audit purposes.
Jim Bentley American Celiac Society [email protected] tel: 1-504-737-3293 --- On Wed, 1/28/09, A. Razzak Memon <[email protected]> wrote: > From: A. Razzak Memon <[email protected]> > Subject: [RBASE-L] - Re: -ERROR- Specified default value is not validfor > column ReleaseDate (2793) > To: "RBASE-L Mailing List" <[email protected]> > Date: Wednesday, January 28, 2009, 10:34 AM > At 10:20 AM 1/28/2009, Alastair Burr wrote: > > >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? > > > Alastair, > > Just curious ... > > When was the last time you did the RELOAD or built a table > or entire database > with a date column having the default value as (.#DATE)? > > Try the following approach when using the .#DATE as > default. > > Example: > > ((IFNULL(DateColumn,.#DATE,DateColumn))) > > This should provide your desired results, even when > updating the record using > the form. This logic is applicable only when a new record > is inserted, which > is similar to the default value. > > Cheers! > > Very Best R:egards, > > Razzak.
