JET ERROR - JOHN VINSON or anyone else who can assist

  • Thread starter Thread starter lawrence ryz
  • Start date Start date
L

lawrence ryz

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.

Any help from anyone would be great.

Lawrence

John,

Okay this is how the database I have created works. I
have created a switchboard which takes you to a form
which enables you to enter data in.

As soon as I tried to type in data all was fine - I set
up a number of pull down menus to select address details
from a lits (I can't remember how I did this as I created
the form some time ago) etc. When I went back to the last
primary key, then I would get that error note. I have
deleted that primary key entry which was blank in any
case - it may be that it was the entry which was causing
me all the problems, I don't know as all seems fine at
present.

So far no problem, but it could be that the lists which I
used and which were in the pull down lists to enter the
data in the forms are too long, don't know.

Thanks as always for your assistance.


Subject: Re: jet database error f.a.o John W. Vinson
From: "John Vinson"
<jvinson@STOP_SPAM.WysardOfInfo.com> Sent: 1/19/2004
4:07:48 PM




John,
This is the error report I get when I go into help.
The error happens when I try an enter data in the next
primary key number.
Click to expand...

Are you trying to type data into an Autonumber field?
Doing so should
not give you *this* particular error, but you
cannot "enter data" or
edit an Autonumber field. Are you using a Form within an
Access
database to do this? or (giving the JavaScript reference)
perhaps are
you using a Web application (it would help a LOT to
indicate what
software you're using if so!)
I have though, no idea why it thinks
there are other users as I don't have any other users
accessing and inputing into the database. Look forward to
your response. Lawrence

The Microsoft Jet database engine stopped the process
because you and another user are attempting to change the
same data at the same time. (Error 3197) This error can
occur in a multiuser environment. Another user has
changed the data you are trying to update. This error can
occur when multiple users open a table or create a
Recordset and use optimistic <JavaScript:hhobj_1.Click() and
the Update method, another user changed the same data. To
overwrite the other user's changes with your own, execute
the Update method again.
Click to expand...

Some suggestions:

- Compact and repair the database
- If that doesn't help, create a new, empty database and
use File...
Get External Data... Import to import all the objects
from this
database into it.



...
 
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.
 
Back
Top