>OK.
>First one is two NT workstations with NT sp3. Another is win98 and WinNT 5 Beta 2. What I an saying is when I have an error on remote machine then in first invironment most of the time I see an error message. Something like:
>"Data type mismatch". In second env. in case of error remote machine does not display error messages which makes it much harder to work with. I thought may be it's a configuration issue.
Mark, several things to do here. First, write or download an error handler that traps runtime erros and logs them to a file or table - VFP provides a wealth of information when runtime errors handled by VFP (as opposed to things that go wrong in the operating system like page faults and memory access violations) occur - with a good error handler, you can actually record the line of code that smoked, the content of VFP's memory variables, open tables and the like. You might want to look at some of the frameworks like Visual MaxFrame that have been released as freeware for ideas; the error handlers in the Visual MaxFrame framework are provided as part of the source code, and do a pretty good job of error logging.
Do yourself a big favor and don't try to develop your COM objects on a beta operating system platform unless you need specific services only available under NT 5/Win2K. If you need NT Server, you can get a 120 day trial version from Microsoft for very little money; at one point in time, you could download the 120 day evaluation version of NT Server with Option Pack 4 from Microsoft's web site; you can order it on CD from Microsoft for not much more than the cost of shipping. If you have Visual Studio 6 Enterprise, it comes with a developer copy of Back Office, complete with SQL Server, Exchange Server and all the other goodies, which is limited to a small number of simultaneous connections.
You can also do your initial development of the COM objects as local out-of-process servers; the same OLE Automation server will run locally as well as deployed on a remote system. Get your VFP code working first before adding the problems of DCOM deployment to your server.
You still haven't told us anywhere near enough to be of any help to you; all we know is that the code doesn't work, and that one of the two environments you listed wouldn't let you see an error message.
