You have the concept right. There's lots that can be done with the UI under COM+ as it's a regular Windows app.
>I'm not sure that completely understand the COM+ concept (maybe just confusion over terminology), so let me explain what I think you're suggesting. I have developed one West Wind Web Connection application, & I think that uses a similar setup.
>
>That application has:
>1. A user interface application which has access to the PC on which the Web Connection "server" application is located. The user interface application has no direct connection to the network data tables, only to the "server" PC.
>2. The PC which contains the "server" application has access to the network data tables. The server application is up at all times, & is accessed by numerous users simultaneously. The server application responds to user requests & returns data (in this case, dynamically-constructed HTML pages.)
>
>One main difference, is that the user interface application in my example is fairly "dumb", whereas the user interface application in the proposed scenario would be fairly complete, except for when it needs to obtain or post data.
>
>Is this anywhere in the ballpark of what you're suggesting?
>
>Thanks,
>Randy
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer