error 3709

[Roy Goldhammer]

Hello there

I've got this error when i run my mde: 3709

The search key was not found on any records

What is that means?

--
øåòé âåìãäîø
òúéã äðãñú úåëðä
èì' 03-5611606
ôìà' 050-7709399
àéîééì: (e-mail address removed)

 

[Allen Browne]

This error indicates that an ISAM SEEK did not result in any matches.

If you get this error in an mdb where the tables are actually Access tables,
and you are not doing any code seeks at the time, it probably means you have
a corrupt index. To fix it try this sequence:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

 

[Roy Goldhammer]

Thankes Allen:

Lavel 1 and two were enough, because the problem was that the field was Memo
and on the sql server it was varchar in side of 1700. I got a new data that
contained more then 1700 records, so i change its size to 7000 and it worked
fine, i also create new mde file and everything was OK.

However, there are many cases that my access is falling down, the corruption
i got was mutch worse: i can't run the access at all, can't compile it,
decompile or ever compact and repair.

The only solutions in that case was to use the last backup i've used
is there a better way to do that?


--
øåòé âåìãäîø
òúéã äðãñú úåëðä
èì' 03-5611606
ôìà' 050-7709399
àéîééì: (e-mail address removed)

 

[Allen Browne]

There's a long list of how to avoid corrupting your database in this
article:
Preventing Corruption
at:
http://allenbrowne.com/ser-25.html

Please take all of those issues seriously.