RAM modules? Swap to find out. BTW, Norton does not always find real problems.
Bad sectors? Run Norton -- use thorough surface test mode. Inappropriate CMOS settings? Reset all properties to default. Just a thought. Stan Loo ----- Original Message ----- From: "Ramsour Mike" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 27, 2002 8:02 AM Subject: RE: Invalid date value (2418) error > Thanks to all who have responded. I am checking out some of the > possibilities. The thing that confuses me the most about the whole Invalid > date error is that it is not consistent. I can run a program, get the error > and then restart the program and get no error. I would think that if it is > really a bad data issue I would get the error every time I ran a given > program. It is very puzzling to me. > > I use temporary tables and views extensively. Could this be a clue? My > database is large by some measures: 800+ mb for RB2 and 200+ mb for the > RB3. Any clues there? I do a reload every morning after all my other > programs run and I do an UNLOAD ALL/RELOAD at least once a week. > > Anyway I'll keep checking. The answer is out there . . . . > > Thanks > > Mike Ramsour > Voice: 1-740-829-4340 > > -----Original Message----- > From: Eric M. Bienstock, Ph.D. [mailto:[EMAIL PROTECTED]] > Sent: Thursday, September 26, 2002 12:48 PM > To: RBASE LIST > Subject: Re: Invalid date value (2418) error > > > > > > > | Periodically I will enter a SELECT statement at the R> such SELECT > |<columns> > | FROM table WHERE date_column BETWEEN 09/01/2002 AND 09/20/2002 and R:Base > | will complain saying Invalid date value. > > Mike, > This behavior would occur if you had an invalid value stored in the > date_column within the date range you specify. It may have gotten there > from some earlier REDEFINE operation, from TEXT to DATE, for example. Or > you may have some stray ASCII characters from some electrical disturbance. > Or your date_column may be a calculated column which evaluates a bad date. > To test these possibilities, see if the error msg depends on the date range, > then look at all your date values in that range. > ... Eric > > -------------------------------------------------------------------------- - > Eric M. Bienstock, Ph.D. > Database Development, etc. > Authorized R:BASE Developer > Eric M. Bienstock & Associates, Inc. > day: 212-978-7948 eve: 973-763-8650(8) > FAX: 775-254-2109 [EMAIL PROTECTED] > http://mywebpages.comcast.net/ericmb/ > -------------------------------------------------------------------------- - > > ----- Original Message ----- > From: "Ramsour Mike" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, September 26, 2002 8:32 AM > Subject: Invalid date value (2418) error > > > | Good morning to all: > | > | I am having an ongoing problem in R:Base (6.5++ for Windows) that is > driving > | me bonkers. The biggest problem I am currently having is that my programs > | which use DATE variables, will sporadically throw an "Invalid date value > | (2418)" error. I say sporadically because I can run a given program and > it > | will display this error and then I can immediately rerun the same program > | with no changes in anything and the error will not appear. I have been > | through my code with a fine-toothed comb and can find no plausible reason > | for this. I make absolutely sure I am using a standard format and my > | variables are all typed at the time of creation. > | > | Periodically I will enter a SELECT statement at the R> such SELECT > <columns> > | FROM table WHERE date_column BETWEEN 09/01/2002 AND 09/20/2002 and R:Base > | will complain saying Invalid date value. I can sometimes place the date > | values in single quotes and R:Base is happy. The frustrating thing is > that > | this is not consistent. Most times it works properly other times it > | complains. > | > | Is there something I should be looking for in my code or is there > something > | going on with R:Base and the way it handles date values -- whether as > | variables or as hard-coded values? > | > | On another note, I run R:Base on a Windows 2000 system. I run nearly 100 > | programs each morning that vary from loading new data into the database to > | printing out reports. It takes about 3 hours for all of the programs to > | run. I can go for days and everything runs perfectly. This week, however, > | R:Base is crashing every morning at various points in the morning update > | routine with a Windows memory error. There are usually 3 separate > messages > | that you have to click through with the final result being that R:Base has > | crashed. The message is to the effect that An error has occurred in RBG65 > | at <memory address>. Windows was unable to read the memory at address > <such > | and such>. > | > | Cany anyone tell me if this is a Windows issue or an R:Base issue? I will > | sometimes get a similar message when I'm running Excel. > | > | My PC has dual 550 mhz Intel processors with 256 MB of RAM. > | > | Any help is greatly appreciated. > | > | Thanks > | > | Mike Ramsour > | Voice: 740-829-4340 > | ================================================ > | TO SEE MESSAGE POSTING GUIDELINES: > | Send a plain text email to [EMAIL PROTECTED] > | In the message body, put just two words: INTRO rbase-l > | ================================================ > | TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > | In the message body, put just two words: UNSUBSCRIBE rbase-l > | ================================================ > | TO SEARCH ARCHIVES: > | http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
