John,

You have confirmed my point. That is that an MTDLL is NOT multi threaded and calling it multithreaded is technically incorrect. It causes confusion as people think it really is.

In a multithreaded app you can spin off a new thread and continue processing while the new thread also does its processing.

An MTDLL is in fact apartment model threaded. You can call it from multiple clients, but those clients will stop and wait for the MTDLL to finish processing. They will not continue to process while waiting for the MTDLL to do its processing. You can also call it from a single client, but it too will stop and wait for the MTDLL to finish processing.

John, you of all people, should know when to use the proper terminology. You've jumped on enough people in the past for not being technically correct.

>The question assumes that an MTDLL is the best way to solve the problem - and that this is a threading issue - it's not. Bascially Craig - you are starting off with a bad premise...
>
>If I wanted this functionality AND - I wanted to use Fox - I would have Fox server running that would poll a table and process incoming report requests -and send them to a specified printer.
>
>The only thing I have to do in the calling app is add a record to a table. Now - if I want some sort of notification deal - there are any number of approaches I could use to deal with that problem: anything from a rudiementary timer mechanism to something more elaborate that would involve event handling.
>
>All that said - if I need free threading - I'll have something built in C++. I believe there are FLL's out there that do this - but I have never tested them.
>
>So...before asking how to do it with an MT-DLL - one needs to ask whether an MT-DLL is the right way to do it in the first place - right?????
>
>< JVP >
>