JET ERROR - JOHN VINSON

  • Thread starter Thread starter Lawrence Ryz
  • Start date Start date
L

Lawrence Ryz

Thanks for your reply John, I did check out the website
that you detailed in your post, I will have another look.

When I installed Office XP, I guess what happened was
that I imported the old access 2000 .mdb files which had
the corruption.

I am happy to create a new database, I guess my only
concern is that I don't have to manually input all that
data which I have spent so much time inputting before.
Are you saying that importing the data from the table
into a new Office XP .mdb file which would then loose the
corruption.

I don't want to do anything too radical if is going to
cause me to start a fresh, but i have noticed that I
can't find do the ctrl + f function to find data without
fixing this Jet error problem.


Subject: Re: JET ERROR - JOHN VINSON or anyone else who
can assist
From: "John Vinson"
<jvinson@STOP_SPAM.WysardOfInfo.com> Sent: 1/25/2004
2:18:18 PM




John,

Further to my post,I am having the same problem again
with the Jet engine.

I am not using a form within an access database to enter
the data. I did do a c"ompact and repair" and got the
following table which was created - "error code -1611
could not find field description." Can anyone else help.

I have also noted that "#######" gets added in one of the
fields in the form of my database. Very strange. It is
then that the jet error warning comes up.
Click to expand...

Your database IS PROBABLY IRRETRIEVABLY CORRUPTED. This
symptom
indicates that the systems tables pointers are messed up,
especially
if the ######## is in a Memo field.

See Tony Toews' Corruption FAQ at

http://www.granite.ab.ca/access/corruptmdbs.htm

You'll probably need to create a new empty .mdb file and
Import
objects, one by one; this table will need to be
recreated. You can
probably (not certainly!) link to the table and create an
Append
query, or more than one, to import all *except* the
corrupted records
- don't import them or you'll just start the problem all
over again;
use the Primary Key of the table to select all records
*except* those
with the ########, and manually reenter these.
 
Thanks for your reply John, I did check out the website
that you detailed in your post, I will have another look.

When I installed Office XP, I guess what happened was
that I imported the old access 2000 .mdb files which had
the corruption.
Click to expand...

That would do it :-{(
I am happy to create a new database, I guess my only
concern is that I don't have to manually input all that
data which I have spent so much time inputting before.
Are you saying that importing the data from the table
into a new Office XP .mdb file which would then loose the
corruption.
Click to expand...

You should be able to *link* to the damaged database and import all
the non-corrupt objects, and the undamaged portions of the corrupt
table. Make backups all along of course!!
I don't want to do anything too radical if is going to
cause me to start a fresh, but i have noticed that I
can't find do the ctrl + f function to find data without
fixing this Jet error problem.
Click to expand...

So don't. Just open the tables in datasheet view (linked), and write
query criteria which select the undamaged data.
 
Back
Top