Bob: You can't test this with TEXT variables, because it has no problem inserting null text values.
AND interestingly enough, doing an "insert...values" acts differently than "insert...select". Here's what I just tested. 1. Started off with NULL = -0-, ZERO ON 2. I created a table with columns AcctNo INT, and Integercol COL 3. SET VAR vInteger INT = NULL, vacctno INT = 5 INSERT INTO testklt (acctno, integercol) values .vacctno, .vinteger This works INSERT INTO testklt (acctno, integercol) SELECT acctno, .vinteger FROM account where limit = 1 This fails with the "an expression cannot end with binary operator" So it has something to do with the way RBase internally parses that command I'm thinking. Changing to ZERO OFF does not change the above command, still an error. Changing to NULL ' ' does not change the above command, just a different error message about incorrect # of values The only way for the insert to correctly work is to: SET ZERO OFF INSERT INTO testklt (acctno, integercol) SELECT acctno, (.vinteger) FROM account where limit = 1 Karen If I have a bunch of null values (text, integer, double, real) and use an insert with ONLY > Karen, > > I have inserted null values before. (Not saying it is best practice, but > it should work) > > I just tested the below . (ver. V8) > > > > R>set var x text = null > > R>set var y text = null > > R>insert into awmlist (location,storenumber) values .x,.y > Successful INSERT operation, 1 rows generated. > > R>sel all from awmlist where count = last > Location StoreNum > -------- -------- > -0- -0- > > > So I believe your inserting nulls is not the issue. > > >
