Can't read information in access DB after using c# code to insert

Question

0.00/5 (No votes)

See more:

This error occurs when an event has failed to run because the location of the logic for the event cannot be evaluated. For example, if the OnOpen property of a form is set to =[Field], this error occurs because a macro or event name is expected to run when the event occurs.

sorry about my english :)

my company has a tool which was coded in access 2003 (File Extension is .mde), day by day i have to type too much so i find a solution, and i figured out that this db .mdb file extension - can be easily accessing without any password, i search on gg and learn how to insert to db access
i was successfull insert into db object but .mde got problem while open it (i guess) with above message

pls help me, i dont know how to fix it

Posted 28-Jan-16 0:00am

Nguyen Khoa Beo

Updated 28-Jan-16 1:26am

Richard MacCutchan

v5

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2016-01-28T02:01:00

If you mean that you have taken an .MDE file that works with Access 2003, and updated it as an .MDB file with a later driver, then the chances are that the file has been corrupted or converted to the later version - which from the point of view of the 2003 application is the same thing.
Think about it: if you buy a 14 year old Ford Fiesta, would you expect the engine parts from a 2016 model to swap right in? Of course not - the design has changed a lot since then. The file is the same: You may be able to read it with a later version driver, but the version it writes will no longer be compatible with earlier software.

I'd strongly suggest that you restore the original .MDE file from a backup, and then either live with the typing, or update the application to a later version.