>Tamar,
>
>We had the exact same problem with a COM DLL last year. What I discovered was that the increase in memory is directly porportinal to the size of strings that you pass as parameters or return from the function. I currently have a client that is experiencing this issue. We have been able to eleminate or reduce this problem by using a table to pass and return strings from the COM DLL. We also reboot the system periodically to make sure things are running well. If you are not doing so already, download ProcessExplorer from the Microsoft SysInternals site. You can see the actual process and it's memory, CPU usage, and IO. You can also download Process Monitor from the same site and it will further allow you to target the problem.

Hmmm, that's interesting. We're calling back and forth a _lot_. I'll see whether I can prove this with some logging.

Tamar