[RBG7-L] - RE: Fw: [RBG7-L] - Data Designer Default Dates

[Dawn Oakes]

Alastair, I tried your _expression_ in one of my tables, a date field.  It does nothing for the data that is already in the table but when new rows are inserted, today's date is put into the field. I imagine if I decided to edit all the other rows in the table the _expression_ would get evaluated and todays date would fill in where it was blank, but I haven't tried. Dawn From: Alastair Burr [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 10, 2004 5:52 PM To: RBG7-L Mailing List Subject: [RBG7-L] - Fw: [RBG7-L] - Data Designer Default Dates I guess that this got missed over the weekend - anybody got any ideas?   Regards, Alastair.   ----- Original Message ----- From: Alastair Burr To: RBG7-L Mailing List Sent: Saturday, August 07, 2004 8:05 AM Subject: [RBG7-L] - Data Designer Default Dates I have been attempting to put this _expression_ - as suggested by Razzak a few weeks ago - into a date field but I find it is not working:   (IFNULL(Up_Date, .#DATE, Up_Date))   The column name is Up_Date and the compute radio button is selected.   In trying to work out why this is not working I have also noticed that two other date fields are not accepting their default values either. Both are date fields with the No Calculation radio button selected and a default value of: 01/01/1900 (date formats: dd/mm/yyyy & ddmmyyyy).   I have tried putting single quotes around the date value which appears to insert the current date rather than the required date and I have also tried putting the value in a CTXT function which isn't accepted but, otherwise, all I seem able to get is a null value.   Does anybody know what I'm doing wrong? (Other fields with text default values are working correctly.)   One other point on the data designer that I have also noticed while writing this e-mail is that if you click back onto the data designer and the mouse happens to be over the radio button group the selected button can be changed. This seems to happen anywhere in the box and not just on a button or its description. Obviously, with care, this is not a problem but if you don't happen to see the change it could easily cause errors.   Regards, Alastair.   ---------------------------------- A D B Burr, St. Albans, UK. ---------------------------------- [EMAIL PROTECTED] ----------------------------------