Hi there!

Here at S.E.A I'm the guy that is responsible for all the stuff you need a
CIN/DLL for. In general, I prefer a DLL when the needed code is large - our
realtime database interface for example. In other cases, for example
providing a hashtable for fast data lookup, I prefer a CIN (and yes, I
often used CINLoad/CINUnload etc. pp.).

The reasons are:
- DLLs can be updated without changing the actual executable - this is
important if you need to debug your code, for example, or provide
several DLLs with the same function calls but different functionality (i.e.
shared memory vs. networked drivers).

- with a CIN, your code is embedded into the VI, and you don't need to
worry about additional files when replacing VI functionalities.

So, for me both concepts do make sense, although of course I could live
with the DLL interface only. Besides, CIN's are generally more difficult to
build.

These are just my 2 cents - your mileage may vary.

Greetings,
Joerg
+------**** Science & Engineering Applications GmbH ****------+
| |
| Joerg Hessdoerfer |
| Leading SW developer Phone: +49 (0)2203-962211 |
| S.E.A GmbH Fax: -962212 |
| D-51147 Koeln Internet: joerg.hessdoerfer@sea-gmbh.com |
| http://www.sea-gmbh.com |
+---------------------------------------------------------------+