Does anyone out there know of any reason why indexes would get whacked
on a daily basis.  I've been helping a client with a Paradox 7 (95/NT)
on an NT network.  At the time of this writing I'm not sure of the NT
version.  Recently the network was upgraded to fast ethernet (10Base100)
with new hubs and all.  Before the upgrade there was an occasional loss
of data and indexes.  After the upgrade it happens at least every other
day.

One user reported the following sequence of events.

The user added a record and was typing in a memo field.
Part way through the typing the system froze and no characters
appeared.  After a few seconds the characters appeared but then the
system locked up.
She was vaugue about how she got out, possibly by persistantly clicking
File -> Exit.  I suspect she might have used the three fingered salute
and chose End-Task when prompted.  The users have been warned repeatedly
that this is an absolute last resort so now if they do it they won't
admit it.
When she tried to get back it, a table that wasn't the focus at the time
of the crash reported an invalid or out of date index.  (She wasn't
sure.)

This is a common scenerio.  Does it sound familiar to anyone?

Pat Levenson

Daniel A. Morgan

Pat: there are many possible reasons for index and
damaged table problems.. hardware, network, user
rebooting, crashes, etc. are possible causes.. there
is no "perfect answer" to that sort of question,
especially with the limited amount of real info that
you have provided..

--
Steve Green - Diamond software Group - Waldorf Maryland USA

and Corel's CTech tech support staffs but I don't represent
Borland International or Corel in any official capacity.