Problem moving Access 97 app to newer versions (97 Sr-2)

Topic

New Reply

I have an Access 97 application that uses an Oracle 8i database as the back end. The Oracle database is being accessed via Oracle ODBC drivers. The Oracle tables are linked in the Access application. I want to move this application into Access 2000 and Access 2002 (XP). After opened the application in Access 2000 and converting it, everything was okay until Access attempted to update the Oracle database via a form bound to a datasheet. The datasheet displays the table records okay. After updating data in an existing records or adding a new record then moving off the record to initiate a table update, Access 2000 crashes with an General Protection Fault. It does not give any error messages. When restarting the application and again viewing the Oracle data with the form, the record added is there or a changes was performed. I cannot figure out why this is happening because I cannot trap an error within Access. Whatever mechanism that controls the Oracle table update must be external to Access 2000. Has anyone had experience converting Access 97 applicatons to newer versions? Is the a definitive guide for the conversion process that describes the pitfalls? I’m at a loss and need to figure this out ASAP. Please HELP!!!

Reply | Quote

Replies

I’ve updated 97 db’s to xp but not with links to oracle but sql server. I would recommend getting the latest odbc drivers for oracle and try deleting and recreating the links to the oracle tables.

Reply | Quote

Thanks for the suggestion but I’ve been there, done that. Didn’t help. Someone suggested using the Microsoft Oracle ODBC driver instead of the Oracle ODBC driver. It’s a no-no in my company to use anything other than the Oracle ODBC drivers. However, I tried the Microsoft driver anyway and the problem still occured.

Reply | Quote

What if you create a new db in 2000 and link to oracle tables and update them. Does it happen then?

Reply | Quote

You aren’t mixing DAO and ADO in the same routine are you? That is a guaranteed crash.

Reply | Quote

The problem is not occurring in code created by me. It is happening within the Access internals that perform updates to Linked tables. That’s why I’m having such trouble figuring out what is going wrong. It is out of my control.

Reply | Quote

Are you by any chance running this on a Windows XP machine? Access 97 (in fact, Office 97) doesn’t really play nicely with WinXP. We see problems on our XP machines at work linking to Access backends. Sometimes it just hangs the entire process for no reason we can see … or it will work one time and fail the next. We haven’t found a good reason or a good cure.

Reply | Quote

Hi Frank,
A number of our loungers work with Oracle and Access 2000/2002 on a regular basis (I only worked with 2 and 97), so I suspect the problem lies somewhere in your configuration or with something unique to your particular database. You mention a form being bound to a datasheet – is that the same thing as being bound to a linked table? Also, how did you create your 2000 database – with the conversion process? The reason I ask is that we have seen problems with that from time to time – you might try creating a new blank database, and then import all of the objects from the 97 database, as that seems to work better. A third question – how much code is behind the form – if it’s a legacy set of code (i.e. Access 2) there are a number of things that can cause problems? Finally, are you getting an actual crash message, or does Access just go away?

Reply | Quote