A new Method '~' of object '~' failed error?

[Chris Franklin]

We are developing an application, which has just moved from VB5 to VB6.

We are selecting data from an Oracle 8 database within a form, which we populate
dynamically, within one DLL (UTI), which is perpetual throughout the life
of the application. Data can be loaded either by double-clicking within a
flexgrid, or by selecting an item and pressing OK. These are both handled
by events in a class. (i.e. by defining variables as WithEvents and setting
reference to the form items).

This data can be loaded from various locations within the system, again within
DLL's.

The system is started from a central executable (CORE), and most DLL's are
started from here - call this MOD1. When loaded from this location all data
appears to be working fine.

If we start a new DLL (TOOL) from within MOD1, we are observing the following
occurences (for data selection within TOOL):
1) Data appears to be loaded correctly in most situations.
2) If we select data by Double-clicking, then redisplay the form and select
data by pressing accept we see the "Method '~' of object '~' failed" (Error
number -2147417848). This is flagged in MOD1, not TOOL as we'd have expected,
and the system then collapses.

Any Ideas?

[Paul Clement]

On 17 Jan 2002 06:23:18 GMT, "Chris Franklin" <chris.franklin@tinyworld.co.uk> wrote:

¤
¤ We are developing an application, which has just moved from VB5 to VB6.
¤
¤ We are selecting data from an Oracle 8 database within a form, which we populate
¤ dynamically, within one DLL (UTI), which is perpetual throughout the life
¤ of the application. Data can be loaded either by double-clicking within a
¤ flexgrid, or by selecting an item and pressing OK. These are both handled
¤ by events in a class. (i.e. by defining variables as WithEvents and setting
¤ reference to the form items).
¤
¤ This data can be loaded from various locations within the system, again within
¤ DLL's.
¤
¤ The system is started from a central executable (CORE), and most DLL's are
¤ started from here - call this MOD1. When loaded from this location all data
¤ appears to be working fine.
¤
¤ If we start a new DLL (TOOL) from within MOD1, we are observing the following
¤ occurences (for data selection within TOOL):
¤ 1) Data appears to be loaded correctly in most situations.
¤ 2) If we select data by Double-clicking, then redisplay the form and select
¤ data by pressing accept we see the "Method '~' of object '~' failed" (Error
¤ number -2147417848). This is flagged in MOD1, not TOOL as we'd have expected,
¤ and the system then collapses.
¤
¤ Any Ideas?

See if any of the following are of help:

http://www.google.com/search?as_q=21...t.com&safe=off


Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)

[Chris Franklin]

Paul Clement <UseAdddressAtEndofMessage@swspectrum.com> wrote:
>On 17 Jan 2002 06:23:18 GMT, "Chris Franklin" <chris.franklin@tinyworld.co.uk>
wrote:
>
>¤
>¤ We are developing an application, which has just moved from VB5 to VB6.
>¤
>¤ We are selecting data from an Oracle 8 database within a form, which we
populate
>¤ dynamically, within one DLL (UTI), which is perpetual throughout the life
>¤ of the application. Data can be loaded either by double-clicking within
a
>¤ flexgrid, or by selecting an item and pressing OK. These are both handled
>¤ by events in a class. (i.e. by defining variables as WithEvents and setting
>¤ reference to the form items).
>¤
>¤ This data can be loaded from various locations within the system, again
within
>¤ DLL's.
>¤
>¤ The system is started from a central executable (CORE), and most DLL's
are
>¤ started from here - call this MOD1. When loaded from this location all
data
>¤ appears to be working fine.
>¤
>¤ If we start a new DLL (TOOL) from within MOD1, we are observing the following
>¤ occurences (for data selection within TOOL):
>¤ 1) Data appears to be loaded correctly in most situations.
>¤ 2) If we select data by Double-clicking, then redisplay the form and select
>¤ data by pressing accept we see the "Method '~' of object '~' failed" (Error
>¤ number -2147417848). This is flagged in MOD1, not TOOL as we'd have expected,
>¤ and the system then collapses.
>¤
>¤ Any Ideas?
>
>See if any of the following are of help:
>
>http://www.google.com/search?as_q=21...t.com&safe=off
>
>
>Paul ~~~ pclement@ameritech.net
>Microsoft MVP (Visual Basic)

Thanks for that, unfortunately I don't think any of those items help.

I had already checked the search engine for ideas, but couldn't find anything
that appliead to our current case

Chris

[Paul Clement]

On 24 Jan 2002 00:27:50 -0800, "Chris Franklin" <chris.franklin@tinyworld.co.uk> wrote:


¤ >
¤ >See if any of the following are of help:
¤ >
¤ >http://www.google.com/search?as_q=21...t.com&safe=off
¤ >
¤ >
¤ >Paul ~~~ pclement@ameritech.net
¤ >Microsoft MVP (Visual Basic)
¤
¤ Thanks for that, unfortunately I don't think any of those items help.
¤
¤ I had already checked the search engine for ideas, but couldn't find anything
¤ that appliead to our current case

Yeah, unfortunately this error may occur in many instances. It might be a bit of a pain, especially
if you're working with a compiled component, but I would definitely attempt to track down the line
of code where this error is occurring.


Paul ~~~ pclement@ameritech.net
Microsoft MVP (Visual Basic)

[dnagel]

I believe I have seen this before due to (in my example)
Oracle Objects for Ole crapping out... It would internally
encounter an error when dealing with the setting of a parameter
that was supposed to take, a date value. The error was actually
due to not explicitly referencing a property and expecting the
default property to do the right thing.

we would use
DBObj.fields("FieldName") = "1-1-2001"
.... and it seemed to work until we used the object again...
....and then the error would occur.

to fix it we would use the full syntax...
DBObj.fields("FieldName").value = "1-1-2001"

What I'm suggesting to you is that somewhere in the DLL,
an error is encountered and not returned back to the calling
process. This causes subsequent calls to give the undefined
error message ~ of ~ failed...

Step line by line through the code and you may still never find it...
....because the problem may have occurred earlier without your
knowledge.

I suggest getting the source and debugging the caller and the
DLL source at the same time to get a better idea of whats really
happening.

hth,

D.

"Chris Franklin" <chris.franklin@tinyworld.co.uk> wrote in message
news:3c466dd6$1@147.208.176.211...
>
> We are developing an application, which has just moved from VB5 to VB6.
>
> We are selecting data from an Oracle 8 database within a form, which we
populate
> dynamically, within one DLL (UTI), which is perpetual throughout the life
> of the application. Data can be loaded either by double-clicking within a
> flexgrid, or by selecting an item and pressing OK. These are both handled
> by events in a class. (i.e. by defining variables as WithEvents and
setting
> reference to the form items).
>
> This data can be loaded from various locations within the system, again
within
> DLL's.
>
> The system is started from a central executable (CORE), and most DLL's are
> started from here - call this MOD1. When loaded from this location all
data
> appears to be working fine.
>
> If we start a new DLL (TOOL) from within MOD1, we are observing the
following
> occurences (for data selection within TOOL):
> 1) Data appears to be loaded correctly in most situations.
> 2) If we select data by Double-clicking, then redisplay the form and
select
> data by pressing accept we see the "Method '~' of object '~' failed"
(Error
> number -2147417848). This is flagged in MOD1, not TOOL as we'd have
expected,
> and the system then collapses.
>
> Any Ideas?

[Chris Franklin]

Thanks for all responses, this error is still unresolved.

The system works fine, until the following line of code is included in the
UTI DLL.
objOWL_Data1.PropValue = mFlexOWLData.TextMatrix(lngRow, DETAIL_POS + 1)

objOWL_Data1 is an instance of one of our classes, also part of the UTI dll,
and is declared using early binding.

This set of code works fine other than in the setup I previously discussed.

The object mFlexOWLData is a local flex grid, dimensioned "With Events" and
pointing to the flex grid on the data selection form.
This is the first reference to the TextMatrix property of the flex grid in
when returning from the parent form.

We do use Oracle Objects for OLE in the system, and have already updated
it to include the .Value as errors were being thrown when using returned
values in strings. I have had a cursory glance at the code, and cannot see
any of these missing.

Chris

"dnagel" <GrandNagel@hotmail.com> wrote:
>I believe I have seen this before due to (in my example)
>Oracle Objects for Ole crapping out... It would internally
>encounter an error when dealing with the setting of a parameter
>that was supposed to take, a date value. The error was actually
>due to not explicitly referencing a property and expecting the
>default property to do the right thing.
>
>we would use
> DBObj.fields("FieldName") = "1-1-2001"
>.... and it seemed to work until we used the object again...
>....and then the error would occur.
>
>to fix it we would use the full syntax...
> DBObj.fields("FieldName").value = "1-1-2001"
>
>What I'm suggesting to you is that somewhere in the DLL,
>an error is encountered and not returned back to the calling
>process. This causes subsequent calls to give the undefined
>error message ~ of ~ failed...
>
>Step line by line through the code and you may still never find it...
>....because the problem may have occurred earlier without your
>knowledge.
>
>I suggest getting the source and debugging the caller and the
>DLL source at the same time to get a better idea of whats really
>happening.
>
>hth,
>
>D.
>
>"Chris Franklin" <chris.franklin@tinyworld.co.uk> wrote in message
>news:3c466dd6$1@147.208.176.211...
>>
>> We are developing an application, which has just moved from VB5 to VB6.
>>
>> We are selecting data from an Oracle 8 database within a form, which we
>populate
>> dynamically, within one DLL (UTI), which is perpetual throughout the life
>> of the application. Data can be loaded either by double-clicking within
a
>> flexgrid, or by selecting an item and pressing OK. These are both handled
>> by events in a class. (i.e. by defining variables as WithEvents and
>setting
>> reference to the form items).
>>
>> This data can be loaded from various locations within the system, again
>within
>> DLL's.
>>
>> The system is started from a central executable (CORE), and most DLL's
are
>> started from here - call this MOD1. When loaded from this location all
>data
>> appears to be working fine.
>>
>> If we start a new DLL (TOOL) from within MOD1, we are observing the
>following
>> occurences (for data selection within TOOL):
>> 1) Data appears to be loaded correctly in most situations.
>> 2) If we select data by Double-clicking, then redisplay the form and
>select
>> data by pressing accept we see the "Method '~' of object '~' failed"
>(Error
>> number -2147417848). This is flagged in MOD1, not TOOL as we'd have
>expected,
>> and the system then collapses.
>>
>> Any Ideas?
>
>