Contact an Expert

Thread: [vrf] Error 979 solution (?)


Permlink Replies: 8 - Pages: 1 - Last Post: Mar 8, 2006 9:21 PM Last Post By: VRF user
VRF user

Posts: 16,231
Registered: 11/05/08
[vrf] Error 979 solution (?)
Posted: Mar 8, 2006 9:21 PM   in response to: VRF user in response to: VRF user
Click to report abuse...   Click to reply to this thread Reply
Wow! Cool detective work. I guess I was pretty much wrong after all - it
seems that the actual cause was this corrupt data even though it did only
come into play when drawing occurred.

I have one more suggestion, given that now you know it's basically a corrupt
data problem. Compare state information from the good copy with that from
the bad copy. This will be found in the .vee file and it looks something
like this:

(device 3 ACTIVEXCONTROL
(properties
(name "Libs, Classes & Functions")
(variableName "gtv")
(objectType "MSComctlLib.TreeView")
)
(implementation
(license 37 #H <some license bytes>)
(state 128 #H <state information bytes>)
)
)

The number after state indicates how many bytes are in the data, two chars
for each byte. If it has to do with corrupt string data, you'll probably
find a missing 0 byte. I suppose there are several other possibilities too.

I'm making a note for VV2 to look into trying to validate state information,
but I don't know how much I can do about it. The state usage is all up to
the individual control.

In any case great work! After I found that Ole View puked on instancing it I
basically gave up.
-SHAWN-



---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".

bwalden

Posts: 176
Registered: 11/11/08
[vrf] Error 979 solution (?)
Posted: Mar 8, 2006 9:33 PM   in response to: VRF user in response to: VRF user
Click to report abuse...   Click to reply to this thread Reply
Following up on Shawn's early comments I discovered that the Red 979
error message appeared when the main body of the GlobalMajic strip chart
ActiveX object was rendered on the display. If I minimized the object, I
could bring it into view without problems (application still wouldn't
run however). If I changed the resolution of the screen so that the
strip chart object was displayed when the application was loaded
(development enviornment) the error occured immediately.

I discovered that I could display the strip chart object's title bar and
this allowed accessing the "Control Properties". Since this error became
a problem when I added a second variable to the chart, I looked at the
control's "variables" definition - the 1st was OK but the 2nd had a
complete collection of strange entries. I fixed these and this solved
the problem (one entry had to be fixed 1st or the Red error poped up
immediately). I could now load and run the application on the "problem"
computers without difficulty.

Here's where it gets tricky - the application with the screwed-up
variable #2 entry runs correctly on some computers and, for these
machines, the variable #2 definition is correct. This implies that the
variable definition is being corrupted on some machines when the
application loads. However, once the problem is corrected on one of the
problem machines, the new code will load on all computers without
further problems.

All I can think of is the possibility that one copy of the application
became corrupted somehow and I haven't been careful enough in keeping
track of what version is installed where. I intend to check this
possibility over the few days since I still have at least one copy of
the corrupted application.

Barrie


---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".

VRF user

Posts: 16,231
Registered: 11/05/08
[vrf] Error 979 solution (?)
Posted: Mar 9, 2006 10:37 AM   in response to: VRF user in response to: VRF user
Click to report abuse...   Click to reply to this thread Reply
Following up on Shawn's early comments I discovered that the Red 979 error message appeared when the main body of the GlobalMajic strip chart ActiveX object was rendered on the display. If I minimized the object, I could bring it into view without problems (application still wouldn't run however). If I changed the resolution of the screen so that the strip chart object was displayed when the application was loaded (development enviornment) the error occured immediately.

I discovered that I could display the strip chart object's title bar and this allowed accessing the "Control Properties". Since this error became a problem when I added a second variable to the chart, I looked at the control's "variables" definition - the 1st was OK but the 2nd had a complete collection of strange entries. I fixed these and this solved the problem (one entry had to be fixed 1st or the Red error poped up immediately). I could now load and run the application on the "problem"
computers without difficulty.

Here's where it gets tricky - the application with the screwed-up variable #2 entry runs correctly on some computers and, for these machines, the variable #2 definition is correct. This implies that the variable definition is being corrupted on some machines when the application loads. However, once the problem is corrected on one of the problem machines, the new code will load on all computers without further problems.

All I can think of is the possibility that one copy of the application became corrupted somehow and I haven't been careful enough in keeping track of what version is installed where. I intend to check this possibility over the few days since I still have at least one copy of the corrupted application.

Barrie


---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
VRF user

Posts: 16,231
Registered: 11/05/08
[vrf] Error 979 solution (?)
Posted: Mar 9, 2006 11:28 AM   in response to: VRF user in response to: VRF user
Click to report abuse...   Click to reply to this thread Reply
Wow! Cool detective work. I guess I was pretty much wrong after all - it seems that the actual cause was this corrupt data even though it did only come into play when drawing occurred.

I have one more suggestion, given that now you know it's basically a corrupt data problem. Compare state information from the good copy with that from the bad copy. This will be found in the .vee file and it looks something like this:

(device 3 ACTIVEXCONTROL
(properties
(name "Libs, Classes & Functions")
(variableName "gtv")
(objectType "MSComctlLib.TreeView")
)
(implementation
(license 37 #H <some license bytes>)
(state 128 #H <state information bytes>)
)
)

The number after state indicates how many bytes are in the data, two chars for each byte. If it has to do with corrupt string data, you'll probably find a missing 0 byte. I suppose there are several other possibilities too.

I'm making a note for VV2 to look into trying to validate state information, but I don't know how much I can do about it. The state usage is all up to the individual control.

In any case great work! After I found that Ole View puked on instancing it I basically gave up.
-SHAWN-



---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
willie.kiely

Posts: 44
Registered: 11/11/08
[vrf] Error 979 solution (?)
Posted: Mar 9, 2006 12:44 PM   in response to: VRF user in response to: VRF user
Click to report abuse...   Click to reply to this thread Reply
< Cool detective work. I guess I was pretty much wrong after all - it<BR>seems that the actual cause was this corrupt data even though it did only<BR>come into play when drawing occurred.<BR><BR>I have one more suggestion, given that now you know it's basically a corrupt<BR>data problem. Compare state information from the good copy with that from<BR>the bad copy. This will be found in the .vee file and it looks something<BR>like this:<BR><BR>(device 3 ACTIVEXCONTROL<BR>  (properties<BR>    (name "Libs, Classes & Functions")<BR>    (variableName "gtv")<BR>    (objectType "MSComctlLib.TreeView")<BR>  )<BR>  (implementation<BR>    (license 37 #H |some license bytes>)<BR>    (state 128 #H |state information bytes>)<BR>  )<BR>)<BR><BR>The number after state indicates how many bytes are in the data, two chars<BR>for each byte. If it has to do with corrupt string data, you'll probably<BR>find a missing 0 byte. I suppose there are several other possibilities too.<BR><BR>I'm making a note for VV2 to look into trying to validate state information,<BR>but I don't know how much I can do about it. The state usage is all up to<BR>the individual control.<BR><BR>In any case great work! After I found that Ole View puked on instancing it I<BR>basically gave up.<BR>-SHAWN-<BR><BR><BR><BR>---<BR>You are currently subscribed to vrf as: Willie.Kiely@bourns.com<BR>To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list,  email "vrf@agilent.com". <BR>If you need help with the mailing list send a message to<BR>"owner-vrf@it.lists.it.agilent.com".<BR>Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".<BR></FONT></P></DIV><BR>---<BR>You are currently subscribed to vrf as: rsb@soco.agilent.com<BR>To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list, email "vrf@agilent.com". <BR>If you need help with the mailing list send a message to<BR>"owner-vrf@it.lists.it.agilent.com".<BR>Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".</BODY></HTML>
VRF user

Posts: 16,231
Registered: 11/05/08
[vrf] Error 979 solution (?)
Posted: Mar 9, 2006 1:00 PM   in response to: VRF user in response to: VRF user
Click to report abuse...   Click to reply to this thread Reply
I would also be interested to know if you think.....Shawn/Barrie, if this is because of the activeX not fully conforming to the ActiveX prorocol?....rather than a Vee problem,
 
or do I have to eat my words.
 
Regards,

  _____  

From: Shawn Fessenden mailto:shawn@testech-ltd.com
Sent: Thu 09/03/2006 18:21
To: VRF
Subject: RE: vrf Error 979 solution (?)



Wow! Cool detective work. I guess I was pretty much wrong after all - it
seems that the actual cause was this corrupt data even though it did only
come into play when drawing occurred.

I have one more suggestion, given that now you know it's basically a corrupt
data problem. Compare state information from the good copy with that from
the bad copy. This will be found in the .vee file and it looks something
like this:

(device 3 ACTIVEXCONTROL
  (properties
    (name "Libs, Classes & Functions")
    (variableName "gtv")
    (objectType "MSComctlLib.TreeView")
  )
  (implementation
    (license 37 #H <some license bytes>)
    (state 128 #H <state information bytes>)
  )
)

The number after state indicates how many bytes are in the data, two chars
for each byte. If it has to do with corrupt string data, you'll probably
find a missing 0 byte. I suppose there are several other possibilities too.

I'm making a note for VV2 to look into trying to validate state information,
but I don't know how much I can do about it. The state usage is all up to
the individual control.

In any case great work! After I found that Ole View puked on instancing it I
basically gave up.
-SHAWN-



---
You are currently subscribed to vrf as: Willie.Kiely@bourns.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list,  email "vrf@agilent.com". 
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".



---

To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
VRF user

Posts: 16,231
Registered: 11/05/08
[vrf] Error 979 solution (?)
Posted: Mar 9, 2006 1:36 PM   in response to: VRF user in response to: VRF user
Click to report abuse...   Click to reply to this thread Reply
I would also be interested to know
> if you think.....Shawn/Barrie, if
> this is because of the activeX not
> fully conforming to the ActiveX
> prorocol?....rather than a Vee
> problem, or do I have to eat my words.

I honestly don't know for sure, but I do know two facts:

There is a problem with this control's conformance. Or at least it doesn't make enough use of VERIFY (not ASSERT, VERIFY). In short, it's error checking is not up to snuff. Were this not the case OLE View would not have a problem instancing it.
Now, the spec doesn't say anything about what conditions you have to VERIFY, but obviously this control makes an incorrect assumption and that's the root cause of it's failure to instance with OLE View. The absolute first thing you do with a release candidate is instance its interfaces with Ole View and check them. This was obviously not done. The control may work fine in most environments, and maybe you'd never run into a problem, but something is very basically wrong with this thing.

There does appear to be some problem with VEE and ActiveX. In version 5, you couldn't use the Forms 2 library. There are still controls that don't work correctly, despite the fact that they work with VB, VBS, Excel, so on and so on. In fact, I have one control I made myself that doesn't work with VEE, though it passes all other tests I've thrown at it. I was going to try to find out why but it's another one of those things I never got around to.
-SHAWN-



---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
bwalden

Posts: 176
Registered: 11/11/08
[vrf] Error 979 solution (?)
Posted: Mar 14, 2006 1:26 AM   in response to: VRF user in response to: VRF user
Click to report abuse...   Click to reply to this thread Reply
Shawn et al,

As suggested, I compared the state information between a good copy and
one that has problems - there are no differences. A simplified version
of my application has a state number of 640 #H and the normal version,
which has a strip chart background picture, has a state number of
465233. These numbers don't change between "good" and "bad" versions.

Barrie


Shawn wrote:
I have one more suggestion, given that now you know it's basically a corrupt
data problem. Compare state information from the good copy with that from
the bad copy. This will be found in the .vee file and it looks something
like this:

(device 3 ACTIVEXCONTROL
(properties
(name "Libs, Classes & Functions")
(variableName "gtv")
(objectType "MSComctlLib.TreeView")
)
(implementation
(license 37 #H <some license bytes>)
(state 128 #H <state information bytes>)
)
)

The number after state indicates how many bytes are in the data, two chars
for each byte. If it has to do with corrupt string data, you'll probably
find a missing 0 byte. I suppose there are several other possibilities too.


---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".

VRF user

Posts: 16,231
Registered: 11/05/08
[vrf] Error 979 solution (?)
Posted: Mar 14, 2006 2:30 PM
Click to report abuse...   Click to reply to this thread Reply
Shawn et al,

As suggested, I compared the state information between a good copy and one that has problems - there are no differences. A simplified version of my application has a state number of 640 #H and the normal version, which has a strip chart background picture, has a state number of 465233. These numbers don't change between "good" and "bad" versions.

Barrie


Shawn wrote:
I have one more suggestion, given that now you know it's basically a corrupt data problem. Compare state information from the good copy with that from the bad copy. This will be found in the .vee file and it looks something like this:

(device 3 ACTIVEXCONTROL
(properties
(name "Libs, Classes & Functions")
(variableName "gtv")
(objectType "MSComctlLib.TreeView")
)
(implementation
(license 37 #H <some license bytes>)
(state 128 #H <state information bytes>)
)
)

The number after state indicates how many bytes are in the data, two chars for each byte. If it has to do with corrupt string data, you'll probably find a missing 0 byte. I suppose there are several other possibilities too.


---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".

Point your RSS reader here for a feed of the latest messages in all forums