I am running AREV 3.0 with the NLM 1.10 on Win 95 workstations under Novell 4.11. I have been unable to fix this problem. The error I start with is: The table is not available FS107 Read Error OS File=…..\REVXXX". I have check the file attributes and flags, ownership, disk… I have copied the file around. I have tried to rebuild all the indexes but get varing results on the different tables some I can copy partial data before getting a FS107 error some I can't copy at all. This is on 4 specific tables. I've tried everything I have discovered on this web site. Anybody have this error before and fix it without loosing all the data?

First thing you should do is get yourself up to the 1.5 NLM. Next I'd check you're running TURBODIS.NLM. After that, it's timeouts on the network, if you're getting this while processing. Of course, I have no idea what you've already tried though.

akaplan@sprezzatura.com

Sprezzatura Group

Ellen ..

I seem to remember having a similar problem some time ago. I traced it down to an incompatibility between Novell Client32 and some NLM that was installed on the server. I got around it by configuring a workstation temporarily to boot under DOS and load the VLM's that DOS would use. Then I got to AREV and expanded the size of the file(s) such that the .OV portion had data. It seemed to me that the error always occured with an attempt was made to read the .OV portion of a file and that the .OV portion was zero length (maybe Aaron's suggestion is to that point). Anyway, I populated the files with dummy data. Went back into windows and wrote valid data into the files and then deleted the dummy stuff. The problem went away and hasn't surfaced again.

By the by .. have you noticed that we are all spending an incredible amount of time diddling with the runtime platform rather than developing and deploying software??? Hmmmmmmmmmm.!

Don Miller

View this thread on the forum...