Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Visual Basic version 6 - Invalid Row Reference error

Visual Basic version 6 - Invalid Row Reference error

Visual Basic version 6 - Invalid Row Reference error

I'm running an application that calls a VB application. The vb app is written in version 5 in about 1998. The vb app connects to an oracle database. I'm needing to move the app to a different server and the new server is running oracle ver. 11.2. When the vb app is called it immediately gives the following error Run-time Error '440'. OIP-04108: Invalid row reference. Does anyone know what could be causing this error? I do not have the source code. I know it's successfully connecting to the database and then trying to read from a table but that's about all I know. Any help will be appreciated.


RE: Visual Basic version 6 - Invalid Row Reference error

If this is a VB5 application from that long ago as it sounds it is likely using RDO to talk to Oracle through some ODBC Driver. If it is using the old Oracle ODBC Driver Microsoft supplies with MDAC that could be the problem due to a poor match with your current version of Oracle.

If the program uses a DSN to define the connection paramaters it might be possible to alter the DSN to use a newer, Oracle-provided ODBC Driver. Then assuming the old RDO objects and the old VB code are compatible with that it might "magically" work.

Without full source code you are probably screwed though. The way life works is that if you do not have the source code a program's lifecycle is over as soon as it stops working. Since you have your old server where it still works you don't have a hairy emergency, just an emergency - even if fiddling with the DSN gets it going temporarily.

Time to put a team on a full reverse-engineering and rewrite. Now.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close