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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DBASE III & Novell 6 file lock problem 1

Status
Not open for further replies.

troona

Programmer
Dec 16, 2003
1
US
Hello All!

We are having a problem in getting DBASE III+ (network version on DOS 3.12 clients) to work with Novell 6 file server.

It works fine with Novell 3.12

When I log on to Novell 6 and try to run any of our applications it immidiately locks database in use with a file lock.
When I stop the program via SUSPEND and type UNLOCK at the dot prompt application then can't even browse database saying that "File is in use by another"???
(I am the only user on the network and all databases and index files have Shared attribute set)

Any suggestions would be greatly appreciated...
Irina
 
Sorry, I don't have a specific answer for you. Do you use the latest Novell clients? Does this do it on all your workstations, such as Win98, WinMe, Win2000, WinXP...?

These comments may not directly apply to your complaint but may give you some helpful ideas:

thread290-497226
Try posting to this thread to see if this person has any ideas!
dBase V Dos on Netware 6.0
If anyone out there runs into problems migrating a dBase V app from Netware 4.11 to Netware 6, I have a tip. If you begin to experience index file corruption on large files routinely, check the setting "CLIENT FILE CACHING ENABLED". It should be set to OFF.

thread182-663740
What "client" is being used? Novell or Microsoft. If using the Novell client there are certain file caching issues to watch out for - make sure TRUE COMMIT is set on in each client. I am assuming you are already using record/file locking in the application.

thread182-100575
rgbean: It's been my observation that especially on Novell networks, that most data corruption was due to either bad network hardware (bad NIC, bad Cabling, bad switch, etc.) or bad configuration of the Novell clients.
 
Hello:

NW6 has two options when volumes are generated and I suspect you have NSS available to you

You should look at NSF (FAT32) type or change the type of network in your database

Hope this helps

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top