Huh? ----- Original Message ----- From: "Emmitt Dove" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Sunday, April 13, 2008 3:20 PM Subject: [RBASE-L] - Re: integer value
> What method was that ... ? > > |-) > > Emmitt Dove > Manager, DairyPak Business Systems > Evergreen Packaging, Inc. > [EMAIL PROTECTED] > [EMAIL PROTECTED] > (203) 643-8022 > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of MikeB > Sent: Sunday, April 13, 2008 2:54 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: integer value > > It's best to start employing some methodology akin to Emmitts especially if > your short term memory is crap like mine anymore... > ----- Original Message ----- > From: "Bernard Lis" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[email protected]> > Sent: Sunday, April 13, 2008 2:06 PM > Subject: [RBASE-L] - Re: integer value > > >> Good idea Emmitt! >> >> ----- Original Message ----- >> From: "Emmitt Dove" <[EMAIL PROTECTED]> >> To: "RBASE-L Mailing List" <[email protected]> >> Sent: Saturday, April 12, 2008 9:20 PM >> Subject: [RBASE-L] - Re: integer value >> >> >>> Variables in R:BASE are by nature global. If you want to have "local" >>> variables, you have to "localize" them by using prefixes that pertain to > a >>> given form or procedure. For instance, by default I start variables with >>> the letter 'v', but in stored procedures will start them with 'p' or 'p' > and >>> 'r' (in an update trigger, for 'prior' and 'revised') so that I can > "CLEAR >>> VAR p%' and not impact my form or calling command file. >>> >>> Emmitt Dove >>> Manager, DairyPak Business Systems >>> Evergreen Packaging, Inc. >>> [EMAIL PROTECTED] >>> [EMAIL PROTECTED] >>> (203) 643-8022 >>> >>> -----Original Message----- >>> From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard > Lis >>> Sent: Saturday, April 12, 2008 8:33 PM >>> To: RBASE-L Mailing List >>> Subject: [RBASE-L] - Re: integer value >>> >>> Thanks everyone for chirping in. I found my problem. >>> I have a button on this form that brings up another form. >>> Closewindow did not work and the second form covered up the first form so > I >>> didn't realize it was still active. >>> I don't understand how any variables in the first form could affect vars > in >>> the second form but eliminating the first form seemed to fix the problem. >>> Bernie Lis >>> ----- Original Message ----- >>> From: "Bernard Lis" <[EMAIL PROTECTED]> >>> To: "RBASE-L Mailing List" <[email protected]> >>> Sent: Thursday, April 10, 2008 10:38 PM >>> Subject: [RBASE-L] - integer value >>> >>> >>>> Hello Experts, >>>> >>>> I have an integer column whose value has become greater than 970,000 >>>> This is the value of our Order Number >>>> So far no problems have been discovered using this number. >>>> I was under the impression that the max integer is 32,767 >>>> >>>> But today I tried to add one to the order number and the order number > did >>>> not change. i.e. set var OrdNo = (.OrdNo + 1) >>>> >>>> Here is my code: >>>> set trace on >>>> set var OrdNo int=null >>>> sel orderno into OrdNo from dbcontrol I get 970115 >>>> set var OrdNo = (.OrdNo + 1) Ordno still is 970115 >>>> >>>> Then I did this >>>> set trace on >>>> set var OrdNo int=null >>>> sel orderno into OrdNo from dbcontrol I get 970115 >>>> set var OrdNo = (.OrdNo + 1) Ordno still is 970115 >>>> set var OrdNo = (.OrdNo + 1) Ordno doesn't change >>>> >>>> Anybody have a GhostBuster team? >>>> >>>> Bernie Lis >>>> >>>> >>>> >>> >>> >>> >> >> >> > > >
