Ria,

I am not sure (at all) what you mean by "file flagging".

For the remainder I will be very very very speculative :

Novell makes use (by default) of the phenomenon Turbofat. It's a "fat" on top of the normal fat. Note : It uses turbofat only when the NFS is not used.

When the turbofat (being physically present on disk) is corrupted, a file will have at least one (Novell) block reference out of order. This means that a number of records (at least one) in your table will contain nulls.
The first thing for you to do is read the table into a hexeditor and scan for nulls below the tableheader. The table header ends at the first (much visible) part not containing nulls by nature (you will see it when you look at it). Looking for nulls means searching for 00h bytes (hex 00).

The turbofat can have gotten corrupted at the moment the files were extracted from the HP database. Or better : when written to Novell's disk.
The clue would be, that this kind of failure will cause the wrong referenced block to be written to by Novell itself, at some point in time. So this is not the timestamp of the official last write access to the table.
Also note that this kind of corruption allows for not "seeing" it. That is, your users may never notice it because of the way Fox retrieves the bytes from disk, which can go around the corrupted turbofat. However, when the corrupted data is in the area of the structural index reference, that may bring the trouble you notice.

But this is all too speculative to be true ...

But, if you expect this to be the case, you can load the NLM TURBODIS at the Novell server, to disable its working with the Turbofat.
Though I can't read it anywhere, it would be my advise to to this in the AUTOEXEC file of Novell (by heart : AUTOEXEC.NCF), and reboot the server.
Things may get really nore slow after this ...

HTH anyway,
Peter



>OS - Windows 95/98/2000
>Novell Netware.
>
>I know that they do some sort of file flagging operation. But I am not sure if that applies to these tables. Will flagging a table make the database not usable.