The right way???

[plawe]

Hi!

Some central applications in our company are written in VB. These
Applications make extensive use of .DLL and .OCX files (also written in VB ourselfes).
Until now these components are installed on every single client machine
(about 250 !).

Now I read that under Win2000 the component could be registerred and served
by one single machine. I think that would make the update process much
easier, because there is only ONE point of maintaining these files.

My questions are:
- is this the way to go?!?
- are there any good online resources to read more about this?
- what other components should be served; only the self developed, or also others like eg. ADO?


I would be very grateful if you could give me some hints on this. Thanks in
advance.

Best regards
Werner

[demirc]

Hi,

I think you are talking about MTS (Ms Transaction Server) , COM+ or .. (Are you ?)

Just to begin with, you can't deploy your ocx's on MTS, only the dll's. And the vb dll's must have:
-their instancing props set to MultiUSE (I would think twice about raising events in those dll's )
-must use apartment threading

If you are looking for links on the subject (MTS):

http://www.microsoft.com/com/wpaper/...#_Toc406484233