MEMO file missing errors since Windows 2000

[wodehouse]

I've added three Windows 2000 professional computers to a network (using a Win 95 PC as a Peer to Peer server) sharing a VFP3 database.

Since adding the PCs I'm now getting regular FPT missing or bad message on different files. I've not had any messages like this before (over two years).

I can repair the files and make sure the Win 95 server is OK. Does anyone know if Win 2000 has any issues that might be tripping me up? Am I missing something?

I'd appreciate your help

 

[TomasDill]

Win 2000/Win NT netowrking had a problem with VFP3 and early versions of VFP 5. The problem was that memo fields got corrupted, specially when editing form and class code snippets. This was because caching. I don't know exactly how to switch off caching, but probably you can find some articles about that at Universl Thread site.

Vlad Grynchyshyn
vgryn@softserve.lviv.ua

http://www.softserve.lviv.ua

The professional level of programmer could be determined by level of stupidity of his/her bugs

 

[dgrewe]

OK, Everyone get ready to tell me I'm wrong again. But here it is again. Win9x/ME and WinNT/2000 use 2 totally different file allocation systems. If you create a file on Win9x and use the foxpro "copy to" command to/from a winNT system (and Vise versa) you will be fine.
BUT
if you use the Windows explorer or (MSDOS) "copy" command to move files to/from a WinNT to any other operating system, Win9x or Novell or etc. You will get this type of problem. WinNT File allocation table IS NOT compatible with any other known operation system except WinNT/2000. WinNT writes information into the file header that other operating system can not read or understand. David W. Grewe
Dave@internationalbid.com
ICQ VFP ActiveList #46145644