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

Windows 2000 causes Error #15 on shared DBF 1

Status
Not open for further replies.

dataccount

Programmer
Sep 19, 2001
39
US
I am using Windows 2000 Professional on a new laptop and encounter this error (Not a table/DBF) regularly on several of my client's peer-to-peer networks where the application DBF files reside on a Windows 98 server. The network protocol used is NetBEUI.

Other workstations on the network running Windows 98 never have this problem and it doesn't make any difference which operating system I use to build the executable. Attempting to open the DBF from the command window on the Windows 2000 machine, with exclusive set off, creates the same error if the file is in use by another person.

I can't believe I am the only person writing applications in FPW 2.6a having this problem. It's probably something really stupid, but if anyone knows what it is, please let me know.
 
No Your not the only one. Everyone that has only half upgraded all the computers on a Microsoft network have this problem. You are using a FAT16 and FAT32 operating system. Fat16 can not read the information M$ writes into the file headers on files/dbf's on FAT32 files.

Answer, make sure all your files are created on the FAT 16 computers. Win2000 uses an updated version of the WinNT HPFAT. David W. Grewe
Dave@internationalbid.com
 
Thanks for your prompt reply. It was not practical to create all of the files on a FAT16 computer, so on the one client I have had a chance to experiment with, I simply upgraded their only Win95 (FAT16) machine on the network to Win98 and converted it to FAT32. Like magic, no more FAT16, no more errors. I hope this works on other clients having one or two old FAT16 machines on the network.

Jim Brown
 
OK, converting all of the machines to FAT32 doesn't work, even after the troublesome tables were recreated. I still get Error #15 - Not a table/DBF when attempting to open a shared .DBF file. For me Windows 2000 just isn't worth the trouble on a predominantly Win98 peer-to-peer network.

If anyone has another suggestion, I would certainly like to hear from you, otherwise Windows 2000 will be replaced by Win98 on this laptop. Thanks.

Jim Brown
dataccount@compuserve.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top