Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP6 on WinXP under Novell Netware
Message
From
12/07/2002 08:39:17
 
 
To
12/07/2002 05:48:16
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00677898
Message ID:
00677951
Views:
22
Some things to try:

On Windows XP workstations go to the Novell advanced client settings properties and turn off the setting for File Caching.

Some info:

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10071902.htm

Also, the latest Novell Client for Windows XP is 4.83. Ensure that it IS the version running because it resolved a lot of conflicts with WIndows XP and Novell.

In addition, On NetWare 5.x make sure you have the latest version of filesys.nlm on the server.

Also a new feature in NetWare 5 SP5 or greater allows us to turn off opportunistic locking at the server console.

?set client file caching enabled = on/off?


Hope this helps,
Tracy


>One of my clients is having trouble running our VFP6 application on his network. He has a mix of workstations, mostly Win98 and has been running successfully for a number of years, with multiple users concurrently accessing a shared databases. He uses Novell 5.3 with the latest Novell Client on his workstations.
>
>He has recently added to his network some new machines with Windows XP Pro installed and found that he gets errors when trying to open the same databases from these new machines. I have tracked down where the error is occuring - here is the code what happens:
>
>lcTabName =
>lcTabtoOpen=lcProjPath+lcTabName+".DBF"
>lcIdxtopen=lcProjPath+lcTabName+".CDX"
>IF FILE(lcIdxtoOpen) AND FILE(lcTabtoOpen)
> * everything ok up to here, but the next line causes a
> * FILE ACCESS DENIED error
> USE (lcTabtoOpen) IN 0 SHARED
> * then obviously the SELECT fails because it isn't USE'd
> SELECT (lcTabName)
>
>Now this doesn't happen every time. When he switches on the machine
>in the morning it works fine. But when he closes the program and runs it again later the error occurs. If he reboots he can usually (but not always) open it ok. The funny thing is that other users on Win98 can always open the databases and never get this error.
>
>
>Can anyone shed any light on this?
.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform