Bob, Been there, tired that. ColumnName always returns ZERO no matter how you retrieve it. There is no way for us to fix this. RBTI must fix the FORMS so that just retrieving a column into a variable will get the true value. Then it could be tested in an EEP.
I've thought of dozens of workarounds, but absolutely none of them will work on a data ENTRY. Since no table record yet exists (all rules must validate before record can be saved) the only way to know the value of a column is to retrieve it into a variable. Catch 22. Dennis McGrath --- Thompson Technology Consultants <[EMAIL PROTECTED]> wrote: > My apologies Dennis, I did not pay close enough attention to your > post! > > What you may be able to do then is set a "check flag" in the > report/form expressions. > Perhaps something similar to this: > > Vchkflag = (IFNULL(columname,'N','Y')) --(Will check to see if > column is null or not) > vtest = columnname --(sets var to > column value or zero if null) > > > Then in your EEP : > > If vchkflag = 'N" and vtest = 0 then > -- Do whatever > > else > > -- Do whatever > > endif > > set var Vchkflag = -0- > set var vtest = -0- > > Return > > > I understand your thoughts on the ZERO ON, but perhaps the > above can resolve your current situation which is what is > important. > > -Bob > > -----Original Message----- > From: Dennis McGrath [SMTP:[EMAIL PROTECTED] > Sent: Thursday, October 09, 2003 6:48 AM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Problems with ZERO ON - Razzak's Reply > > Nice try, but I thought of that. By the time the eep executes it is > already too late. The problem is getting the value off the form into > a > variable. > > Dennis McGrath > > > --- Thompson Technology Consultants <[EMAIL PROTECTED]> wrote: > > Dennis, > > > > I have not "checked" this out, but since you are looking at > using > > EEP's > > in your form, a possible solution is to simply put "Set Zero Off" > as > > the first > > line in your EEP and then Set Zero ON before your RETURN. > > > > I believe this setting is "session specific". I.E. no other users > > working on > > the database would be affected when this setting was toggled on or > > off. > > (I did check out this and the setting is session specific) > > > > >
