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

[Alastair Burr]

Thanks, David, but it's not the DEFAULT that I'm trying to get to work. This is copied from Razzak's post a while back:   Alastair, MY emphasis was on DEFAULT values. "The default values that are expressions are NEVER supported in R:BASE." You should have no problem when defining values as "Compute" with correct "_expression_" as demonstrated in RBG7 sample ConComp Database. Database: ConComp Table: AllColumns Column: CComputedDate Type: DATE Compute : Checked _expression_: (IFNULL(CComputedDate,.#DATE,CComputedDate)) Very Best R:egards, Razzak   I'm trying to use this _expression_:   (IFNULL(Up_Date, .#DATE, Up_Date))   which, to me looks the same except for the column names. The data designer accepts the _expression_ and saves it but nay new row added does NOT get the value inserted.   Regards, Alastair.   ----- Original Message ----- From: David M. Blocker To: RBG7-L Mailing List Sent: Tuesday, August 10, 2004 10:53 PM Subject: [RBG7-L] - Re: Fw: [RBG7-L] - Data Designer Default Dates Alastair   you can't use an _expression_ as a default value in a table defintion.   You can only do this with a form _expression_ or eep on the form, or by loading a row into the table with the default value via a program and then calling the form   David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: Alastair Burr To: RBG7-L Mailing List Sent: Tuesday, August 10, 2004 5:51 PM 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] ----------------------------------