At 06:30 PM 8/13/2004 +0100, Alastair Burr wrote:
Thanks, Razzak.
Yes, I did notice and, as I said, I copied & pasted your code - no changes whatsoever - into a command file which I then ran to create the table.
I have since created a new database and created the same table the same way in that which gives me the same end result.
I will see if I can write up the _exact_ keystrokes that I am doing and then send the db to RDCC with the explanation.
Actually, it was with a form that I first noticed the problem. I went back to the data designer to ensure that it was correct there first before I tried the form again. It was in subsequent testing in the browser that I got the problem. In theory, the defaults should never be used - they are set at 01/01/1900 to indicate something is wrong - but when I tried to add the expression and tested I then found the defaults on the two other fields were not working correctly. I am fairly sure that the expression problem was caused by having had a default for that column beforehand which I did not clear when I added the expression and, since clearing the default, that part of the problem is solved.
Alastair,
Many thanks for your continuing testing as well as the feedback!
I have been doing some internal testing too.
No worries!
Very Best R:egards,
Razzak.
