Karen, I usually try to use the NULL keyword in INSERT statements where appropriate, so that the INSERT won't be at the mercy of the last form or program that fiddled with the NULL display or ZERO setting. I guess the amper-variable approach must need the whole INSERT command built in the variable to work there.
Bill On Mon, Mar 15, 2010 at 12:04 PM, <[email protected]> wrote: > Bill: that doesn't work for me, get a message when trying to insert the > variable into the Real column that "column BillRate must be a valid REAL" > > Can I ask: do you ever have Insert statements with variables that could > possibly be null? Or do you test them all? > > Karen > > > Karen, > > One idea: you could do this: > > > IF vBillRate IS NULL THEN > SET VAR vBillRateText = 'NULL' > ELSE > SET VAR vBillRateText = (CTXT(.vBillRate)) > ENDIF > > > And then replace .vBillRate in your insert with &vBillRateText > > >
