[Babaseannounce] Bad CYCPOINTS data in Babase for the last week

Karl O. Pinc kop at meme.com
Sat May 13 01:19:02 EDT 2006


Hi everybody,

I'm writing this to babase-announce because it effects
all babase users.

I've had a bug in my conversion program (to Babase 2.0) so for the last
week.  The CYCPOINTS.Source column was wrong, and, more
importantly, automatic Mdates were not properly added to CYCPOINTS.
I have now fixed this.  This has resulted in a lot more
automatic Mdates which translates to a lot of changes
in CYCPOINTS, which CYCPOINTS are aggregated into
cycles, and the content of the REPSTATS and
CYCSTATS tables.  If you've been running queries
using this data in the last week then your results
are off (although probably pretty close to what
you'd see if you ran them in foxpro (Babase 1.0)
because it has no automatic Mdates).

You may wish to run your queries again.

Sorry about that.


Karl <kop at meme.com>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein



More information about the Babaseannounce mailing list