Paradox and Windows NT 
Author Message
 Paradox and Windows NT

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



Fri, 08 Oct 1999 03:00:00 GMT
 Paradox and Windows NT

Quote:
> 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.

You don't know enough for anyone to give you a good answer. Get the
version of NT and find out which service packs have been installed. Get
the version of Win95 and find out which service packs have been
installed. Also see if any of the Win95 Plus Packs were installed. Then
get back to us. There is no reason on a properly set up system why you
should be having any problems with indices.

Daniel A. Morgan



Sat, 09 Oct 1999 03:00:00 GMT
 Paradox and Windows NT

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.



Sun, 10 Oct 1999 03:00:00 GMT
 
 [ 3 post ] 

 Relevant Pages 

1. Paradox 7, Windows NT, 2000, XP

2. Paradox Under Windows NT Terminal Services

3. paradox 5.0 (windows), NT and printing...

4. LOCKING OF PARADOX UNDER WINDOWS NT WITH SP4

5. Paradox and Windows NT

6. Paradox and Windows NT

7. Paradox and Windows NT

8. Paradox and Windows NT 3.51

9. Paradox and Windows NT

10. Paradox on Windows NT - Workstation hangs on db search

11. Paradox 5 and Paradox 7 under Windows NT

12. Paradox 7.0 for Windows and Windows NT OS


 
Powered by phpBB® Forum Software