Anyone ever got that in a pure VBA system?
I’ve seen it when using dlls and trying to pass byRef when the dll wants it byVal. (well in fact in most of the cases mentioned here). But I don’t recall seeing it in a pure VBA project that isn’t using dlls (or non standard references).
Anyway Codecleaner fixed it (Thanks Rob)
I always worry though, that something deep inside may be going horribly wrong quietly.
I couldn’t get the code to break on the problem line, it just seemed to get upset returning from a function call.
I very rarely have problems with VBA, but there are one or two projects I look after that throw freaky errors quite regularly. How about you?
cheers
Simon
Smurf on Spreadsheets 
Thursday, 13th December, 2007 at 7:33 am |
I get plenty of spurious ‘Duplicate Declaration In Current Scope’ errors. This obviously stops the code dead and I have to close and reopen the workbook at least, though it makes sense to run CodeCleaner.
I did have one VB6 project that contained a phantom persistent breakpoint that I could never get rid of. I never worked out how it could possibly persist across compiles even after I cleared out all temp files.
Thursday, 13th December, 2007 at 2:19 pm |
Rob
I don’t think I have ever seen that first one, but I have had the zombie breakpoints.
Thursday, 13th December, 2007 at 4:46 pm |
Yup, had this too but only rarely. Usually when a spreadsheet was about to crap out (technical term) from being compiled too many times. The Export/Import objects has typically fixed it. The only expectation was a form with a corrupted third party ocx which wouldn’t export. Had to resort to a back up copy for that object. Funny, the Export/Import usually fixes those phantom break points too.
Thursday, 13th December, 2007 at 6:50 pm |
My personal favourite was “the object involved has disconnected from its clients”, which I got fairly regularly on one of my workbooks. Or the enigmatic “automation error”…
Thursday, 14th July, 2011 at 11:13 am |
I got hit by the Bad DLL calling convention error today, in a pure VBA project. Codecleaner sorted it out for me too…