"Al Vas" <forgetit@forgetit.com> wrote in message
news:E8EA4138-5599-450C-8B35-6EEAB5CF3AE1@news.elevatesoft.com...
> Fair enough Tim.  I guess though, if index issues are caused by our code,
> then it will be no different if we upgrade to 4, so it might be wise for
> us to start investigating before we move to 4.?  Has anyone had
> experiences with indexing issues caused by their code in Version 4?

Anything is possible, but you have no direct acess to indexes, so in all
probability the problem is in DBISAM, not in your code. As I recall, the bug
(if we're talking about the same thing) was introduced in one of the later
versions of V3, and persisted thru the life of the product. The symptom was
a corrupted index in a high activity multi user table. Something to do with
an index page not being written to disk when it should, as far as I can
recall.

If you use C/S, you will get other benefits upgrading to V4. I had several
problems with the V3 server, but the V4 server works like a charm.

Robert

Alex,

<< Fair enough Tim.  I guess though, if index issues are caused by our code,
then it will be no different if we upgrade to 4, so it might be wise for us
to start investigating before we move to 4.?  Has anyone had experiences
with indexing issues caused by their code in Version 4? >>

It's most definitely not being caused by your code.

--
Tim Young
Elevate Software
www.elevatesoft.com