mikanu wrote: I figured it must be related to the open database process since it's the first db-related operation in my code and it try the methods provided by the MSDN, I cant dig any deeper as my dev computer is boxed up waiting to be moved... DEBUGGING : Removing the needles from the haystack.

Well... it seems that not a lot of people took interest in this post, nonetheless have I got an answer. Anyway, I found the answer on another forum and thought to complete this post with the explanation and some thoughts. Basically, the problem was using the InterlockedExchange64 instead of the regular InterlockedExchange. Some say that the InterlockedExchange64 is designed for 64bit OSes and that's the reason it was making my assembly not load. That sounds interesting, but what's even more interesting is that the DLL was compiling without problems with the 64bit version of the function. It's a mistery. Also it's interesting that the IntelliSense is picking up InterlockedExchange64 but not the regular one... definetly something odd. :wtf: Enough said, I can now load the assembly in the Evaluate Tool and it looks good so I'm on to further testing it.

If what you want to do is write a web crawler to collect information, why reinvent the wheel? Why not use a web browser control. You didn't specify any language restrictions, so you can start with the article on Code Project: http://www.codeproject.com/internet/httpget-post.asp?target=winsock%7Cweb%7Cbrowser[^] or try http://www.syix.com/wpsjr1/wsksock.zip[^] RageInTheMachine9532