Corrupt Exe files & insufficient error messages
I generally have no problems with VB5, there are only two really annoying things with it:
- Sometimes when compiling to an exe I experienced that the exe file is corrupt and I had to recompile. But I could see this effect only if my PC was running over days and I am doing much with activex also from 3rd party. Maybe something remains in memory in background after some code breaks during programming and makes the troubles later. Further I am compiling and developing the same projects on up to 3 different machines. It may also be that on some machine some DLL is not up to date which I know also to make some problems (but this cannot be addressed to VB only). So maybe this doen't address the plain VB5 only.
- Sometimes when I am compiling an activex dll created by my own with binary compatibility I get error messages "Ambigous name detected" although I cannot find ambigous names. Worst of all VB doesn't show the position in code where the problem occurs so I have to look at the latest added functions. Mostly the problem is solved by commenting out all latest added functions and then recompile. Then remove the comments of one function and recompile. Then the next function and so on. But - I only have this problems with one of my activex DLLs and it is very large (compiled 1,3 MB).
I also never had IDE hangups (execpt for some times when a third party module hangs up), I only experienced IDE problems with VB6.