VBGamer

No, the DLL was pure VB. I had one program that was a form and a class module - the class module had some array access in it (simulating memory access of a surface). When running as a compiled EXE it took 413-540ms to complete. The DLL was an ActiveX one; in VB that just means having a class module run as a seperate program (sort of). This had the same Class module file. When it was linked to the EXE and run it took about 250ms to 360ms - between 35 and 40% faster.