
Possible answer to Err 49: Bad DLL calling convention
For the record:
I've had an elusive error # 49: "Bad DLL calling convention." Couldn't
trace it to its offending code line as usual.
A Google search turned up a helpful thread from October 1999 in this
newsgroup, which I paste in below.
I followed the advice of Wojtek Korycki (below), which didn't work.
However, when I did a decompile (using command line switch) then recompiled,
it did work.
So, problem fixed, this time, by doing a decompile, then recompiling.
I am running Access 2002 using Access 2002 file format, under Windows XP
Professional.
Hope this will be helpful for someone else.
Mark Hammer
Lake Oswego, Oregon
================
Subject: Access200 - Error 49: "Bad DLL calling..."
Newsgroups: microsoft.public.access.modulesdaovba
View this article only
Date: 1999/10/08
From time to time I get error 49: "Bad DLL calling convention" for no
apparent reason. I figured that if I comment out the code where the error
occurs, compile, then uncomment that code, and recompile again - that fixes
the problem (at least for a while).
Any idea why the error 49 occurs and how to avoid it?
(another Access bug?)
Woj
Message 2 in thread
Subject: Re: Access200 - Error 49: "Bad DLL calling..."
Newsgroups: microsoft.public.access.modulesdaovba
View this article only
Date: 1999/10/08
I have seeen this fairly regularly.... it is coming from
inside VBE. I do not know of a workaround, but I have seen
it in both Excel and Access.
--
MichKa