Fatal exception

[Cakkie]

I have this problem. I'm working on this program that uses RDO, and a datagrid. The datagrid is in unbound mode, so the updates must be done manually. This is done in a procedure. All went fine until a few days ago. Now, whenever the update method of the resultset object is called, the program exits with a fatal exception in rdo20.dll

I,ve tried several things, like reinstalling rdo, reinstalling vb, installing another service pack but none of them work.

Help appriciated

Tom Cannaerts
[email protected]

Programming today is a race between software engineers striving to build bigger and better idot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning -- Rich Cook

[Cimperiali]

>>All went fine until a few days ago...
Did you install anithing else in the meanwhile?

Special thanks to Lothar "the Great" Haensler, Tom Archer, Chris Eastwood, TCartwright, Bruno Paris
and all the other wonderful people who made and make Codeguru a great place.
Come back soon, you Gurus.

The Rater

[Cakkie]

Well, it is being developed on this very special configuration, it was started way back in VB3, upgraded to VB4, installed some Sheridan Data Widgets, upgraded those widgets (these are just ocx files), upgraded to VB5, installed servicepack 2.
As you can see, this is a very unhealty situation, and was only available on 1 machine.
Of course, this machine crashed, actually it didn't, or at least not at first. At first it just didn't compile the program anymore, giving an error on WinOldApp (aka a dos program), which was running C2.exe (aka the vb compiler). So we decided to try and install the entire bunch on a seperate PC, all seemd to work fine, until we started to test the applications, and on some places (the datagrids, where I do the update manually), it gives the error. So we tried runing it again on the development machine (the original, the app worked fine in the IDE, even with the datagrids) and you could guess what happened, it didn't work.

So I guess it has got something to do with refferences, but I can't figure out which one. My guess is DAO, there might be a different version on the 2 machines, but the funny thing is that now it doesn't work anymore, even with the old version, knowing that the code has't changed.

Tom Cannaerts
[email protected]

Programming today is a race between software engineers striving to build bigger and better idot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning -- Rich Cook

[Cimperiali]

Stop doping your Pc!
;-)
Sorry, do not know how to help. It seems as if registry is quite dirty (your machine seems to be confused about correct ocx to use). You may try unregistering the grid and then registering the one you need again, but I will never accept that software to be installed on my machine (too dangerous). May be it should be better to rewrite it all in same language with same version and using only latest thirdy part controls...

Special thanks to Lothar "the Great" Haensler, Tom Archer, Chris Eastwood, TCartwright, Bruno Paris
and all the other wonderful people who made and make Codeguru a great place.
Come back soon, you Gurus.

The Rater

[Clearcode]

You could try running the VB SetupWizard on the first machine and creating an installl that you then run on your second (newer) machine.

Then reinstall the TP components that require licenses.

HTH,
Duncan

-------------------------------------------------
Ex. Datis: Duncan Jones
Merrion Computing Ltd
http://www.merrioncomputing.com
Check out the new downloads - ImageMap.ocx is the VB control that emulates an HTML image map, EventVB.OCX for adding new events to your VB form and adding System Tray support simply, MCL Hotkey for implemenmting system-wide hotkeys in your application...all with source code included.