Bill,

>>That make's two of us. What are you doing? VB or C#. It's the latter for myself.
>>
>C# mostly in ASP.NET. They're kind of "web-happy" here, seeing every need as a web application. Sort of like the guy who has only one tool, a hammer, so, of course, everything's looking like a nail. :-)

Don't get me wrong. I still think Fox has a place in the .NET environment, especially if there's a lot of data munging going on. IOW, a bunch of different reports with different data groupings based on the same data set.

For example, if the reports are for the same time period in SQL Server (or other backend), pull the data once into VFP. After that, either build the query string, or use SET ENGINE BEHAVIOR 70 with a query containing all the fields, to generate the result set. Then pass it back to .NET via XML.

In my mind, this should scale significantly better, regardless if you're using COM Interop or a Web Service, than making < n > trips back and forth between the client and the server, or the client, Web server and the data server.

>>Well, I'm not so sure I understand the mechanism either. I recently (the past month or so), switched to a new laptop and can't recreate the old situation.
>
>Yes, I'm still scratching my head on this one. The only way it'll work on my machine is to entering the actual machine name. None of the localmachine variations ( localhost, (localhost), local, (local), etc. ) work. If there is a switch switched somewhere I don't know what it is but would sure like to. If I learn anything else on it I'll let you know.
>
I'd appreciate that.

Regards,