"1/1/3999 BCE, the earliest possible R:Base date." I love it! Seriously, when I kept getting this problem with the report, I finally created a view and drove the report from that. It brought the information out the way I wanted it
That report caused me a few more headaches in getting it to print to a file so I could incorporate the report data into a WordPerfect document. Three times out of four I got dumped completely out of R:Base and had to restart everything. But I finally got the job done; maybe not too elegantly but it's finished. Thanks, Bill, for your reply. Dick Croy Bill Downall wrote: > Nothing to do with your threshhold. Something is wrong in your > expression that determines the date, or in your data. > > What you are seeing is a null date. 12/31/4000 is really December 31, > 4000 BCE, which is the day before the earliest possible R:Base date, > January 1, 3999 BCE. You probably have zero set on, which makes > R:Base try to interpret the null as a zero, which is then converted to > that date. > > Is your break value evaluated in the same section as the field is > located? > > Bill > > On Tue, 10 Sep 2002 14:08:55 -0400, Richard S. Croy wrote: > > >But when I pick up the date in a break variable, it consistently comes > >out as 12/31/4000! > > -- Richard S. Croy [EMAIL PROTECTED] ================================================ 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/
