Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > microsoft.public.excel.programming > #108852

Run time error '49': Bad DLL calling convention - solved

Show all headers | View raw

I run Windows Vista, Excel 2003 and code in ...\XLSTART\PERSONAL.XLS.
Some days ago, I hit this error. I solved it by Export File in the
Visual Basic Editor, deleting the offending sub and importing it again.
All very tedious and error prone.
I've had the error a second time.
I started going through my old microsoft.public.excel.programming posts.
In response to "Excel startup problem. Possible problem with
stdole32.tlb" of "26 September 2011 12:39:49", Jim Cone suggested
>Two things you haven't mentioned that should be done...
>1.  Clearing out the Windows Temp folder... Start | Run | %Temp%
>2.  Deleting the Excel11.xlb file - usually found near (on Windows XP)...
>     "C:\Documents and Settings\~name\Application Data\Microsoft\Excel"

I deleted most files from %temp%.
When deleting folders, I got a report a folder was shared.
The deletion took forever and I forced a shutdown.
I restarted and tried again.
I got another forever and went for a 10 minute coffee.
Safe mode got me down to a single file.
The problem remained.
Deleting excel11.xlb was ineffective.

I reported "Code Cleaner menu entry disappeared" on 21 July 2013
12:16:24 and was unable to solve the issue.

When I first hit the bad DLL problem, I diarised
20160524 orlando.mvps.org vba decompiler

I downloaded and applied that.
My PERSONAL.XLS was reduced by about a third and the bad DLL problem
went away.
-- 
Walter Briscoe

Back to microsoft.public.excel.programming | Previous | Next | Find similar | Unroll thread

Thread

Run time error '49': Bad DLL calling convention - solved Walter Briscoe <wbriscoe@nospam.demon.co.uk> - 2016-05-28 07:08 +0100

csiph-web