How should I implement a COM component that I am using for a middle tier
(business rules layer)

Should I compile this as a separate DLL, or as a Visual Component to be used
in VB??

If I use it as a DLL, is there any way of putting it on the control palette,
and changing event code etc from there??

Any help appreciated

Thanks

1. If this component will run on the same computer as the client app, you can
have a dll or exe or user control.  If it runs on a different computer, it has
to be exe.

The choice is really dictated by:

1. Is there any reason to run it as a stand alone application? If yes, it is
exe.
2.Will you use it with COM+?  If yes, it is dll.

Will you make  life for many developers easier if you provide visual interface?
usually business rules tier does not have any run-time interface (that what
presentation layer is for).

MSDN has a whole section on when to use which.  The same section has
step-by-step how to test both exes and dlls.

--
Laura Meyerovich
Magnet Systems
phone (401) 742-1636
fax   (520) 438-5537

Visual Basic, MS Access, Crystal Reports, SQL Server, and ASP independent
consultant.
Development, system integration, database design and data conversions.

well...
middle tier components are actually the logic of yr application wich means
they will not have interface (usually) and they will have to be programmed
so it will be easiest way to replace them without changing teh rest of the
application.
there is nothing special about writing a middle tier component except those
facts....also usually in n tier application you will use MTS to control yr
components - to transact logical components and database connection
components...if you are using mts - yr component must be a dll component if
not...depends...usually you will set it as an exe..

hoped i helped..

orit