What does “Method '~' of object '~'

Question

I'm trying to run a legacy VB6 application on my desktop (it doesn't have a user interface, being a command-line app), and when I do, I get a message box saying

Run-time error '4099':

Method '~' of object '~' failed

This means nothing to me; does anyone have an idea what is going wrong?

Answer 1

That can happen when supporting libraries (dlls or ocxs) are not registered properly or the versions of the installed libraries are different (and incompatible) with the version the app was compiled against originally.

Make sure all dependent libraries are registered and the proper version.

You may have to recompile the app to make it work with newer versions of the supporting libraries.

Answer 2

I had this Problem for a While.

I looked for a Answer and This WebPage was Top of Search.

A Moment Ago.

I uninstalled Office 2000 Toolbar

Uninstalled Visual Basic 6 and Removed all But not MSDN

Reinstalled Visual Basic 6

But I always Had My Clipboard Logger Program in Visual Basic 6 was Running

and Found That Was The Error

Without that Running I don't Get the Error

Method of "~" Object "~" Failed

When Starting Visual Basic 6 IDE

After Running The Clipboard Code VB6 Program with Ctrl F5

Start With Full Compile

and Cured of Compile Errors in the Code

But Still With Problem Loading VB6 IDE

Until I Put - Option Explicit Through Whole Clipboard Code

Except One Module That was too Big to Complete Quickly

But Especially in the Class Module

That Had some Undeclared Variables

and Then That Cured It

That's My Personal Solution and Contribution to This Web Log

An Additional Update and Edit Here

After Reading the 3 Threads of This Subject One of Here about the Clipboard https://stackoverflow.com/a/8577499/5226365

and I spotted the Bug Again Testing Again

As This Is My Clipboard Code

and I was Annoyed at VB6 IDE Using the Clipboard at Load Especially When Carrying a Clipboard Into Code

and I made The Code Intercept the VB6 IDE Load of a Bitmap and Put back what was there Before

Now I have to Be More Considerate in my Code and Wait for the Splash Screen to Finish with "Findwindow"

I Think I solved That Now

I have got a Professionally Written ClipBoard Source Code that I Think Uses API

That I Hunted Down and Have Yet to USE

It Seems a Pain in My Code That I have to Search

For i = -30000 To 32000
    i2 =  Clipboard.GetFormat(i)
Next

To Test If False

For ClipBoard-ed Object's in the Form Designer

So they Don't Get Crippled or Interfere With My Code Program

My ClipBoard Program Code is the Only Long Lasting Program Left that I Run Always

For ClipBoards From the Internet Pages

and It Takes / Logs Clip's of Pictures BitMaps of Screenshots and Things Storing in Date and Time Files

I wish I Knew More about How to Get Drag and Drop Info Out

Hope This Helps

2015 Aug 14 8am-9am

Answer 3

For a VB6 program which is run as a command line application there is an extra stage required after compilation: the VB6 linker needs to be run on the executable to set it as a console program:

<VB6 dir>\LINK.EXE  /EDIT  /SUBSYSTEM:CONSOLE  <program>.exe

Failure to do this will give the Method '~' of object '~' failed error when the program is run.

Answer 4

I have VB6 SP6 and I can reproduce this behavior. In a fresh project, put this code into a form. The project runs normally with F5. Right click the project and select Publish then Build Outputs. This generates the error message.

Option Explicit

Public Sub Init()
    Dim blnErrorHandling As Boolean

    If False Then
        blnErrorHandling = True
    Else
        blnErrorHandling = False
End Sub

Now comment out the last four lines:

Option Explicit

Public Sub Init()
    Dim blnErrorHandling As Boolean

'    If False Then
'        blnErrorHandling = True
'    Else
'        blnErrorHandling = False
End Sub

You no longer get the error and the outputs are built normally. I was quickly adding in some error handling to locate the source of a crash and If False Then is perfectly valid. The MDAC checker said all was ok and a reboot didn't solve the problem.

Answer 5

Another cause can be when using automation, some minor-version mismatch of Office:

I have a legacy VB5+Access app (which i'm in the process of rewriting in Delphi and replacing all the automation mess with clean OpenDocument generation) that ran well on some systems and gave the error on others.

This error would happen when generating an Excel spreadsheet, and seemed harmless (except the annoyance and as it would show a dozen times the risk of user clicking 'Abort' in the middle) as if always clicking 'Ignore' everything worked as expected.

I eventually found the cause was the way Office 97 was installed:

The error would show up if the Office 97 setup sequence was:

• Office 97 SR0 install CD
• apply SR1 patch
• apply SR2 patch

but not if it was installed with:

• Office 97 SR1 install CD
• apply SR2 patch

Doing an uninstall / reinstall with SR1 setup on the affected systems solved the problem.

Answer 6

As per my experience, it is due to Microsoft Access Version.

My program was made in MS Office 2007 and installed newer version of MS Office. Thats why this error appears.