By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,968 Members | 1,852 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,968 IT Pros & Developers. It's quick & easy.

Problem with Find Button has Returned - Heeellllpppp!

P: n/a
Hi all

Bit of an obscure one this, but hopefully someone will be able to help.

4 years ago we had a potentially catastrophic problem with our Access
database.
From memory it was written in Access 2000, but is now used on Access 2003.
The problem surrounded the Find button created using the wizard. There was
some issue with this procedure and linked tables.

Similar symptoms are now occurring. That is:

The user tries to find an existing record either to amend it or, if it
doesn't exist, to add it to our database.
The find button does not return a record, so the user assumes it does not
exist in the database and tries to add it.
On trying to leave the primary key field the user is informed that this
record does exist and cannot be added.

In 2002, the solution was found in a patch jet40sp5_9xnt.exe.
Surely by now this error and the fix provided by that patch would have been
incorporated into Access2003?
It doesn't make sense to me to apply this old patch to software that is
almost 5 years on.

I have checked the version of Jet running on each of the machines reporting
problems and they are all 4.0.8618.0 which I believe is the latest patch for
WinXP.

Anyone got any ideas on where I can find a solution for this please.

My concern is that this issue caused strange behaviour of the database last
time including entry of data against spurious records etc.

TIA

Phil
Oct 26 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi,

some questions:
Does the find-procedure filters out soms records ?
if not, did you try to compact/repair the database for repair of
damaged indexes ?
if this all is not the cause of the problem some info on the used query
(SQL) or table definition is needed to solve this question. If a form
is involved some info about the design of the form (at least the fields
involved) will also be needed for an answer.

Marc

TheScullster schreef:
Hi all

Bit of an obscure one this, but hopefully someone will be able to help.

4 years ago we had a potentially catastrophic problem with our Access
database.
From memory it was written in Access 2000, but is now used on Access 2003.
The problem surrounded the Find button created using the wizard. There was
some issue with this procedure and linked tables.

Similar symptoms are now occurring. That is:

The user tries to find an existing record either to amend it or, if it
doesn't exist, to add it to our database.
The find button does not return a record, so the user assumes it does not
exist in the database and tries to add it.
On trying to leave the primary key field the user is informed that this
record does exist and cannot be added.

In 2002, the solution was found in a patch jet40sp5_9xnt.exe.
Surely by now this error and the fix provided by that patch would have been
incorporated into Access2003?
It doesn't make sense to me to apply this old patch to software that is
almost 5 years on.

I have checked the version of Jet running on each of the machines reporting
problems and they are all 4.0.8618.0 which I believe is the latest patch for
WinXP.

Anyone got any ideas on where I can find a solution for this please.

My concern is that this issue caused strange behaviour of the database last
time including entry of data against spurious records etc.

TIA

Phil
Oct 30 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.