×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

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

Jobs

Unexpected Error 35012

Unexpected Error 35012

Unexpected Error 35012

(OP)
Hi

I am getting message "Unexpected Error (35012)" when I try and open a VBA module in Access 97 (SR-1).

I can find no reference to this error code anywhere. It has happened before and the only way I could fix it was to create a new database, copy what I could from the old database and rewrite all the areas which were not useable. This was on a seperate module the the one that is not accessable this time.

Can someone point me in the right direction for this error?

All the best

Keith

RE: Unexpected Error 35012

Corruption... I've had that one before. Your best bet is to re-install Access and rebuild the database as you have suggested.
Rob Marriott
CCTC1
rob@career-connections.net

RE: Unexpected Error 35012

(OP)
Hi

Thanks for that. I feared as much.

Any idea of what causes this error? Anything I can do to prevent it happening again. Making a .MDE is probably not an option (due to a severely limited application accessing the tables).

All the best

Keith

RE: Unexpected Error 35012

Hi,
 I really can't say what causes it. When I was hired at the company I am working for now the first project that I was given was to finish a database that someone else had written 95% of. They were in the process of making me an office so for the first few weeks I was working in the computer lab at one of the computers. When I found this problem I was told to contact Microsoft by my employer. Programmers don't call tech support =), so reluctantly I phoned. As I had figured they did not have a clue what to do about it. So, I rebuilt the database on another computer with Access and never had the problem again.
Rob Marriott
CCTC1
rob@career-connections.net

RE: Unexpected Error 35012

Hi,

I have the same problem...When you talk about rebuilding database are we talking about creating a new database and copying all forms,queries from corrupted one into it or are we actually talking about building everything from scratch !

Ta,
Dave.

RE: Unexpected Error 35012

Hi,
 Just creating a new database and copying the objects (less the problem ones) into it.

Rob Marriott
rob@career-connections.net

RE: Unexpected Error 35012

Is it possible that running a multiuser database over a network may cause corruption in a form.  In this case is it wise to split a database in 2 having forms in one and tables in another using linked tables?  The forms would be held on local PCs and linked to data held on a server.  The forms would load quicker and also not have to travel over the network.  If the database was corrupted then only the forms database would need to be replaced on the local PC possibly from an opriginal stored on the server.

RE: Unexpected Error 35012

No, not necessarily. Access is not a true client/server database. It is documented that the maximum number of concurrent users is about five. You might get away with five to ten, however the more users connected to the database, the more unpredictable the results.

Splitting the database into a back-end and front-end will give a performance increase, however, you are still simultaneously accessing the tables. You have to understand exactly how Access stores the database objects and records: all in one big blob of a file. As you work with data, adding and deleting, the database becomes fragmented internally just like your harddrive does. You run a repair and compact on the database, like you would defrag your harddrive, to do some garbage collection and re-ordering.

I would agree that removing the forms and such via splitting the database would cut down on the possibility of corruption by minimizing the amount of processing being done on one particular mdb file. But remember, no matter what type of data you are accessing within a database, be it records or forms, there a still little file pointers moving through the database constantly reading and writing. I am actually surprised that corruption doesn't happen more often.

I don't personally know the inner schematics of Access because that information is for privileged, paying, 3rd party developers. But I can tell you that the "form" is not actually corrupt, but rather the portion or segment of the database in which for form itself sits.

Using the database that I mentioned previously as an example: One year later I was contacted by several different companies who were using the database with complaints that they were losing data. When the last person closed out of the forms, they received a message stating that the form had changed. When they clicked "OK", they lost all of their work. Now how could the form change if they were only entering data and they did not go into the design view?

Corruption, it's like a cancer. When I rebuilt the database a year before, by transferring the so-called non-corrupt objects over to a new empty database file and re-writing the corrupt forms, another object, believing it to be unaffected, must have been situated in this corrupt area of the mdb file. And when imported, brought the corruption over with it. The form that caused error 35012 was probably taking up 80% of the corrupt area, while the form that silently slipped by perhaps only had 20% of its structure stored in the corrupt area. I know this is the same occurrence because we sold 50 copies of this database and all 50 caused this same problem. No one bothered to report it to me earlier.

No one can be sure what causes corruption, as there are too many probable causes: a bad Access installation on a users machine, a computer crash, too many users connected at once, etc. I have seen more cases of corrupt tables than forms, which is to be expected.

Rob Marriott
rob@career-connections.net

RE: Unexpected Error 35012

I have seen this also. I fixed it by using the /decompile command option. This is not a documented command line parameter, but it works.

Under Start, Run enter Msaccess.exe /decompile "xxx"

where xxx is the full path of your corrupt mdb file. Make sure you include the extension (.mdb).

Try this and let me know how this goes.

John

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