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!

Application Error on executing code 2

Status
Not open for further replies.

Magnetar

Programmer
Sep 22, 2001
73
GB
Morning

Could someone advise me on the best action to take please?

I have written some code which enables me to calculate then write data to certain fields. This has been fine until this morning when I received the following error msge:

"DR WATSON FOR WINDOWS NT

An application error has occured and an application error log is being generated.

msaccess.exe
Exception: access violatioln (0xc0000005), Address: 0x65233a04"


The version of Access I'm currently developing is Access 97, on a shared network drive.

I did call the relevant helpdesk person(s), who suggested that the error may be within the code, or perhaps the file is currupt.

However, my code has been working okay up until now.

[All the procedure does is this: It looks at a file number entered into one table (B), selects (from another table(A)) some fields related to the same file number, performs the relevant calculations, and places the result back into table (B). A function was called from within the form, for the calculation. I have had no problems with the procedure/code up to now!].

Please help!

Cheers Mags
 
A lot of times, the kind of problem you describe is not an ongoing one. Sometimes, the problem is with windows and not with the code you've been successfully using. Do a compact and repair on the MDB first. Then close and restart windows on your machine. If you STILL have the problem, create a new empty DB and then IMPORT everything out of the original Db with the problem. For some reason, this frequently realigns whatever has become "confused". The new Db usually will work properly as before. "Databases That Work The Way You Do!"
 
I hate that one......

One thing I found is if you are referencing an object that alreadt exsists int he DB when you're copying, that error will fire off.

For example, of you have a Module called DBUser, and use the following code :DoCmd.CopyObject rst2.Fields(0).Value, "DBUser", acModule, "DBUser

Dr. Watson will fire off.... Tyrone Lumley
augerinn@gte.net
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top