I'm assuming you're referring to the Inoculan product you can run as a service on an NT4 server. Well, only one client of mine uses this product, and they don't use VFP, so I can't comment on that particular use.

However, a version they installed about 6 months ago blew out their MS Proxy Server 2 installation. As in, caused MSPS to fail on startup; this could only be fixed by reinstalling it after the Inoculan installation. A huge PITA. This information was not on their site (needless to say) and was admitted to by their tech support only after sharp and focused questioning.

According to support documents on their site, the Inoculan installation replaces several NT .DLLs, including WININET.DLL which can cause older versions of IE to fail. I suspect this or some other unspecified .DLL replacement causes the problem with MSPS.

My suspicion is that this product has not been sufficiently tested for real-world use on typical NT servers. Lean hard on their tech support for answers. I would ask them for a complete list of all NT .DLLs replaced by their product, and how it interacts with the latest NT service packs and various patches.

Good luck.

>I am wondering if anyone has noticed any problems involving VFP and Inoculan.
>
>We use SBT accounting software, version Pro 5.0, which is done with VFP 5. We recently had a number of almost random errors. They seemed related conceptually. Some would complain that a file could not be read. Others would complain that a file could not be opened or didn't exist. Sometimes the NT Redirector would time out.
>
>At first I thought it may be a bad network card, but it wasn't. We tested our cards (both workstation and server), and we re-routed our network wires though a different hub. Everything tested fine...and had no effect...we still got errors.
>
>Then we thought it may be an errant program. We identified a likely candidate and discovered that sometimes it wasn't running in it's own memory space. We fixed that...and still had problems.
>
>We tested our data files and everything opened and browsed properly. We had SBT reindex all of it's files and that didn't help either.
>
>We decided to restore the SBT system back to it's state of 2 months ago...when we did not have this problem... We thought that would either place the blame firmly on hardware or software/data. If we still had the problem then that would indicate it was hardware...
>
>We still got the same errors.
>
>There was still one thing to check. We had a service on the server, which had been active for a long time, which we could turn off. We had previously made adjustments to it, and later "unmade" those adjustments...so we thought that cleared the service of responsibility.
>
>We turned off the service and the problems went away...
>
>Maybe the "problem" is still there and the service is just the "final straw"...but the errors no longer occur.
>
>Maybe we'll move the service to another machine.
>
>The service we turned off was Inoculan...our anti-virus software!
>
>Has anyone heard of any behaviors like this?
>
>We've used Inoculan for a long time and this is the first time we've had this problem.
>
>Rick Liebespach