Quote Originally Posted by dilettante View Post
1. The easiest way is to create a non-Form Class that in turn loads/shows the Form. But you do not want one thread for each file (whatever "received" file means)!!! Threads are not cheap, and most of the time more than a single worker thread doesn't make sense and will actually slow everything down.
Inside the WNPROC (if you checked my code above) , i will get the file name that was selected from windows context menu and it's at this moment that i called it file received, i mean i received the file name that was selected by the user inisde my WNPROC....In other word, i refere to the select cases code that is inside my WNPROC

A VB6 ActiveX EXE can self-register on its first run.
That's exactly what I want, can you give me an example on how to do that ? and how to use the "/regserver" commad ?
Because I want to make a standalone exe so it will be very usefull that it register itself


So far I don't see anything indicating you will benefit from all of this. Threads are not some kind of magic. Your idea of creating a thread for each of hundreds or thousands of workloads is frightening, to say the least. Most likely you'll lock up or even crash your PC, or at best have things run very slowly.

Me neither, but I have to check and see if in reality it will change or not .. By the way, i won't really make a thread for each file, only for files that I suspect that they will take long time to be treated, for expl, folders that include subfolders and in each lots of files