Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / General 2 / June 2006



Tip: Looking for answers? Try searching our database.

Visual Basic Run-time error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Steve Louie - 26 Jun 2006 07:25 GMT
I get two VB Run-time error often on my Windows XP computer.  On both, the
Debug button in the dialog box is gray out.  This happens most loften when I
have Word or Excel 2003 open.  The errors are as follow,

Run-time error '5':
Invalid procedure call or argument

Run-time error '-2147417843 (8001010d)':
Automation error
An outgoing call cannot be  made since the application is dispatching an
input-synchronous call.  

I searched MS KB but cannot find anything on them.  Any insight as to what
exactly Run-time errors and how I can fix them would be grately appreciated.  

Steve
Robert Morley - 26 Jun 2006 18:27 GMT
Typically, I would think the errors are arising from some DLL that's
referenced in your app.  It probably can't debug them because the errors are
happening in the code of the DLL instead of in your code itself.  I could be
wrong on that, but that's where I'd tend to look first.

Run-time Error '5' happens a lot when there are multiple objects or
functions with the same name in your code, or if a DLL is missing, so look
at those possibilities...try fully qualifying your function calls and see if
that resolves anything (i.e., not just "Recordset", but "DAO.Recordset" or
"ADO.Recordset", or instead of "Left$()", use "VBA.Left$()", etc.

Chances are that Word or Excel have nothing to do with it, but certainly
they could if you're referencing those DLLs in your app.

If you can't figure it out, your best bet is probably to step through your
code and figure out specifically where it's happening (and if it's
reproducible if you run the program again without changing anything else).
Worst case scenario, put a bunch of Debug.Print statements into your code
(or send debugging info to a file...whatever), and use that to figure out
where exactly it's happening.

Rob

>I get two VB Run-time error often on my Windows XP computer.  On both, the
> Debug button in the dialog box is gray out.  This happens most loften when
[quoted text clipped - 14 lines]
>
> Steve
Mark Yudkin - 28 Jun 2006 18:03 GMT
You're trying to access a remote component during a paint (or similar)
event. Don't. This is forbidden.

BTW, I had no trouble using search.microsoft.com to locate KB131056
(http://support.microsoft.com/kb/131056/en-us) and KB198996
(http://support.microsoft.com/kb/198996).

>I get two VB Run-time error often on my Windows XP computer.  On both, the
> Debug button in the dialog box is gray out.  This happens most loften when
[quoted text clipped - 14 lines]
>
> Steve
Robert Morley - 28 Jun 2006 22:31 GMT
Ah, yes, I'd forgotten about that little foible!  Thanks for reminding me
(and the OP as well, of course).

Rob

> You're trying to access a remote component during a paint (or similar)
> event. Don't. This is forbidden.
>
> BTW, I had no trouble using search.microsoft.com to locate KB131056
> (http://support.microsoft.com/kb/131056/en-us) and KB198996
> (http://support.microsoft.com/kb/198996).
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.