Since you are limited as to the solutions, the only thing I can suggest is a settings change. This really only applies to running FP DOS 2.x, but what the heck. In the Network Neighborhood Properties, select the Novell Client and click the Properties button. Under the Advanced Settings tab, scroll down to the bottom of the listbox. Change the UseExtendedFileHandles to On.

How are you accessing the 2.6 tables from VFP? ODBC? Are you using the latest MS FoxPro Driver? My version is 4.00.4403.02.

>Dear Y'all,
>
>A customer of mine who had a FPW2.6 app has two of their users testing the rollout of their new VFP app. This is my first VFP app in production and so I am a bit of a newbie when it comes to any issues to do with troubleshooting.
>
>These two users are having 1 to 2 "hangs" a day with the VFP app. These are *not* code problems as our previous few weeks of testing have caught most of these (and no error routine is being triggered, at least). They seem to get hung up in Word97 or they have even had the odd hang in the app itself (once when they were in a search screen and VFP was off searching an index - in 2.6, this was sometimes the case with a corrupted index but the index did not appear to be corrupt as it could be used by other users).
>
>Here are what they are using:
>
>1 person on Win95, 1 on Win98
>both on Novell 4.12 using Client 32 ver 3.1 as the client
>Word97
>Excel97
>Groupwise 5.5
>
>The hang in Word97 is fairly consistent ie. 1 time out of 10, when they go to save something in Word and the "Save As" dialog comes up, the machine hangs as it is trying to read a network directory. This sortof seems like either a a) Novell Client 32 problem reading a network directory for whatever reason. Unfortunately, the latest version of Client 32 causes a printing problem in another critical app at this company so I cannot even try that.
>
>Basic questions to stimulate thinking:
>1) anyone have any specific issues with Word, specifically Word 97
>2) any problems with not enough memory in machines (one has 64mb and the other 128mb and MEMLIMIT is set to 40% in config.fpw)
>3) If it get them to stop using the VFP version and go back to the 2.6 version, no hangs so it is definitely a VFP problem or general problem with Windows that manifests itself by running an app that is much bigger etc
>
>Thanks,
>
>Albert Gostick