On occasion I get the above message when I try opening a project on the network. 90% of the time I am the only one that gets into that project. DSummZZZ no need to answer you already have seen it. The file is not marked read only. If I try maybe 10 times it finally opens. Any Ideas or suggestions. This only happens on my Win 2000 box using VFP6.0.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Project File Read Only
- Thread starter jaa69
- Start date
![[neutral]](/data/assets/smilies/neutral.gif "[neutral] [neutral]")
- Thread starter
- #3
Since a Project file is always opened exclusively, and NT / 2000 servers will always try to cache an open file, until it times out, the server will treat it as though someone (else in this case) has it open!
Get the network administrator to change this time out setting, and while this will unnecessarily close some files too soon, you'll be able to open your project.
Rick
Get the network administrator to change this time out setting, and while this will unnecessarily close some files too soon, you'll be able to open your project.
Rick
- Thread starter
- #5
Hmm,
That sounds good, but this is running on a Novell Server 5.00. Workstation is Win 2000 Pro. Have not had this problem on any other machines except this. Other users like DsummZZZ does not seem to have this problem at least he does not complain about it like I do. Has anyone experienced this type of behavor on a 2000 Workstation. The project is on the Server. Even went as far to check to make sure the server did not say I had it open. After 10-15 trys it seems to let me in. It is more frustrating than anything else.
That sounds good, but this is running on a Novell Server 5.00. Workstation is Win 2000 Pro. Have not had this problem on any other machines except this. Other users like DsummZZZ does not seem to have this problem at least he does not complain about it like I do. Has anyone experienced this type of behavor on a 2000 Workstation. The project is on the Server. Even went as far to check to make sure the server did not say I had it open. After 10-15 trys it seems to let me in. It is more frustrating than anything else.
Ah, Novell! It also has timeout configurations to be adjusted. (You can have the administrator check to see who the server thinks has this file open/locked.) Also, to make sure you don't have problems (especially if the workstation hasn't been updated to SP3), make sure you reset the default caching parameters on the client. If you are using the current 4.83 client for NT/2000/XP, go to the advanced settings tab and make sure "File Caching" is OFF, and "File Commit" in ON.
Rick
Rick
- Thread starter
- #7
Note: I wasn't implying the client changes would fix the "locked" file problem, but rather you may get file corruption without them! You'll still need the network administrator to help you determine if it's really a timeout configuration problem. When it's unavailable, have them check it's status with console monitor to determine who has the file open. If it's you, then you may need to tweak some additional client properties.
You didn't say, but you are using SP 5 with VFP 6.0 aren't you?
Rick
You didn't say, but you are using SP 5 with VFP 6.0 aren't you?
Rick
- Status
Similar threads
- Locked
- Question
