Compiling Client app for COM+

[RSchweitzer]

Do I install the COM+ proxy on the client machine, reference it in the cient app project references and then compile it and make my distribution package or are there other issues involved???

[ilynx]

when you refer ur com+ in your program, that will be an early binding issue and it is not recommended when creating com+. use late binding option using createobject(). of course there are also some issues like security, etc. set the proper roles and your ready to distribute.

[RSchweitzer]

Thanks for the reply. I didn't know that early binding was discouraged for a client/server application, in fact, I thought it is preferred!Can you go into alittle more detail why or point me another reference.

However, my specific question is, having built a client proxy and installing it on the client machine, do I reference this when compiling my client app for distribution??

[ilynx]

i don't get the picture. are u using MTS??? is your application a three-tier application or simply client/server. make a more broad description of your problem.

[JHamilton]

You would use:

Dim myObj as Object

set myObj = CreateObject("MyCOM+.MyClass")




no need to set a reference, tho you'll lose Intellisense. Late binding is preferred in distributed apps for compatibility reasons. It is more loosely bound than early binding, so it is a little safer, albeit, slower.

Software is like sex, it's better when it's free - Linus Torvalds
Software is like sex, it's better when I get paid for it. - me

[RSchweitzer]

Here's the scoop: the app is a three tier distributed application to manage training records. A user interface written for administrators will be installed on client machines and access the middle(business tier) running on a COM+ application (configured component) as well as a Data Access Component running in an application as well in COM+

I want to distribute the User interface application, have it reference the proxy DLL exported from the Business Component. It all works fine on my development machine but when I install in on another clean test machine to simulate a client install I get an error starting the application # 458 variable uses an automation type not supported in VB. I first install the proxy DLL and then the user interface installation package. Start it up and get the above error.

[JHamilton]

Is your client a 9x or NT 4 sp3 machine? If so, you'll need to install DCOM on 9x and sp4 or greater on NT 4.
http://www.microsoft.com/com/tech/dcom.asp

If that doesn't solve it, try early binding on your client.

Software is like sex, it's better when it's free - Linus Torvalds
Software is like sex, it's better when I get paid for it. - me

[RSchweitzer]

The test machine has win98. DCOM was installed 1st and all objects use early, vTable binding. One curious thing was when the proxy was installed a tmp file, APL22.tmp, was in the ComPLUS Applications folder. Do you know what this file is for and is this normal?

I can't think of anything else to try???

[JHamilton]

I'm at a loss on this. I don't know if the tmp file is normal. Sorry.

Software is like sex, it's better when it's free - Linus Torvalds
Software is like sex, it's better when I get paid for it. - me