Quote Originally Posted by DataMiser View Post
...VB6 I think compiles each routine as it is called so you can have quite a lot of freedom in editing a routine so long as the current code execution point is not within that routine. When it is VB6 will usually tell you that you need to restart the program to apply the changes.
That is not correct. You can also make many changes in VB if the code is kept in the currently executed procedure. It is only problematic in wrapped lines (with _ at the end of the line), in with-constructs and in the select-case conditions. Of course, you may not delete a variable that has already been initialised, but you must declare and use new variables.

Note on memory: As a 32-bit system, VB can only address 4GB and must share this memory with the operating system. This is why VB6 does better on a 64-bit system, because (theoretically) it does not have to share the 4GB.

Ideal environment for VB6: Win7 64Bit (without Aero) + 8GB memory or more. W. Wolf