>>>My database container became corrupted for the 2nd time in two weeks. I noticed the last modified date on the database was 1:30pm on friday. How can I find out which user id wrote the change to that file (corrupted the file)? The database is on a netware 4.1x volume.
>>>
>>>Note: all of the tables were fine, just the database itself was corrupted.
>>
>>Evan,
>>
>>I don't think that the user is the problem, but Netware 4.x (and Client 32) there's an article on it on Novell's site. Just do a search for FoxPro.
>
>I will take a look at the article, thanks. We have been running Netware 4.x and Client32 since they came out (years) with no problems, then all of a sudden bam! Two database corrutions in a row.

Evan,

I sympathize, believe me, I've had my own set of problems with Client 32. These include table corruption, index corruption, Win386 read errors with FPW. My experience with the corruption leads me to believe, that the larger the size of the table/index, the more likely this is to occur. These problems don't occur with MS's Client. Novell seems to think it has to do with the number of file handles FoxPro uses (which can be quite large). Further, they state that Netware 5.x fixes the problem. As we say in the states, Evan, "I'm from Missouri" (meaning I'm skeptical) on this. I'll believe it when I see it.

For me (and my users), not to mention the network guys, this is a major league PITA. From the moment I laid eyes on Client 32, I didn't like it. For my money, it's too difficult to control, and simply too agressive.

>So, netware doesn't keep track of the user/process/service that last modified a file?

Somethings they do track, others I believe so. I don't know which category this would fall into.

>Thanks for your help.