Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database with GUI in Access: Fatal error

Status
Not open for further replies.

alcae

Technical User
Sep 12, 2008
3
PT
Hi there.
I have created a database in Oracle with a GUI in Access. The form consists of 10 subforms. It worked for some time, but now when I try to add a new record in any of the submenus (clicking on a command button or on the navigator) it gives me an error and ends the programme.
Can anybody help me on this?
Thanks in advance..
 
it gives me an error
Any chance you could post the error message(s) ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
Thanks PH for your advice to improve my question.
The error that I was talking about is "Microsoft access has encountered a problem and needs to close. We are sorry for the inconvenience."
I don't understand why this happens suddenly after I have inserted only a few records in the DataBase. I have already tried with versions 2003 and XP of Access. For a while it works fine and then it gives me that message error whenever I try to add a new record..
 
Probably one of the first things to try is the old create a blank database and import everything into it. Amazingly, this will often cure the corruption blues!

Here's a couple of links on this particualr subject:



The Missinglinq

Richmond, Virginia

There's ALWAYS more than one way to skin a cat!
 
I tried the suggestion made by Missingling and Joe and .. no news, unfortunately .. without any warning, it crashes again and appears the same board telling: "Sorry about the inconvenience ..". I really don´t know what else to do because never happened something like that with other databases made in Oracle and linked to Access interface.

I will try to find another solution to the problem.

Thanks to all, anyway

 
You can try Missingling's solution again, except import one object at a time. It may at least tell you which specific object(s) is corrupt (i.e. the object that causes the crash is the one that is corrupt).

You may be able to import all objects but the one that is corrupt.

Joe Schwarz
Custom Software Developer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top