>Ed,
>
>Reading my original post I'd realized that I'd said VFP when I ment FoxPro (we have applications in both Foxpro 2.6 dos and windows and VFP 6). That's the reason I ruled out NETRemoteTod and DCOM. So I guess that the file time scenario is my answer, either I like it or not.
>Do you know any way of using DCOM with foxpro 2.6, because we are now working with another project were DCOM would be the best solution, but it'll work only with VFP?
>

FPW is a Win16 app, which means COM isn't available. THe only way I could see to use it would be to write a 16 bit .DLL or .FLL which 'thunks' some 32 bit process, which then would handle the DCOM. Not something I'd want to do unless there was lots of money, and I didn't have to guarentee it would ever work reliably. Given exiting problems with FPW anf fast processors, and other issues which might arise and remain broken since FPW is no longer supported, I'd stay far away from new development with FPW>