Re: Default user ID in SQL table

Can answer one question - a blank field is a field WITH a value - all blanks. A field without a value - I assume you mean one that is NULL - could have anything in memory or on disk, but it has a flag that says we do not know what its value is. Also, this is a different usage of the word, null, than it is when applied to pointers.

Regards
Vern

Rick.Chevalier@xxxxxxxxxxxxxxx wrote:

I can see that I didn't phrase my original question correctly. Maybe Duane has the right answer but I'm going to try this one more time to see if there are any other thoughts.

I really am only interested in the field values on add. I asked the change question already. What I want to know is, I think, really two parts.

Part one is why don't I get the default values when adding records using DBU? Duane's answer does make sense; I just thought a blank alpha field is the same as not having a value. Maybe not.

Part 2 is why do I get errors when replacing the USER special register with SYSTEM_USER or SESSION_USER? The SQL reference seems to say they are pretty much the same thing. Using SYSTEM_USER or SESSION_USER in place of USER results in a 'token not valid' error on the comma ending the line.

Hopefully this will clear things up some.

Rick

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.