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

FPW2.5 & Win2000 sharing is corrupting files! HELP!! 1

Status
Not open for further replies.

MJJ

Programmer
Jul 27, 2000
13
BH
Hi All,
Once again, I need some help. One person in a team was recently upgraded from Win98 to Win2000. Everyone else in the team has Win98. This team links together via Ethernet hub to share DBFs and APPs.
1) This Win2000 person can see other people's files, but they can't see her files... more importantly - 2) On 2 occasions, the person with Win2000 linked with the others, started FPW2.5, set path to ...(someone else on the team's mapped drive)..., started the APP, & corrupted several DBFs on the other person's HD. I have not witnessed this because it just happened on the field and I'm not physically there. I was told there were "several error messages", but they can't seem to remember to write these things down to tell me what they are.
Anyway, the end result is when they try to open the DBF, it errors with "Memo file missing/invalid" and can't open the file again. The APP does routine backups, so not too much work was lost...
But has anyone else experienced this?? Is this inherent to mixing Win2000 & Win98 & FPW25 & sharing files? Or will I continue to have this problem if everyone goes to Win2000 & uses FPW25 & shares?? Any insight would be greatly appreciated!
 
To help with your database not a table and memo file missing problem see the FAQ section of this forum FAQ 2a.
As far as why this happened. In every foxpro forum I frequent, this same issue is being discussed. MicroSoft dropped support for DOS with the release of Win2000 and the reason is becoming clear in these forums. Win2000 is NT and will only run on the new 128 bit HPFS. The HPFS adds information to the header of files. DOS 16 bit applications are having a hard time with this 128 bit file allocation system. The only 3 fixes I have heard of at this time are:
1. Remove Win2000 and revert back to Win95 or Win98.
2. Upgrade the application to VFP.
3. Rewite the application in a non-MicroSoft database application.

David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top