problem

[freelancer]

I recently posted a question (see below) which unfortunately nobody seemed to
be able to help me with. Further to this question I have noticed that my
primary table now has two records which have a JobID number which are the
same ‘zero’ number. I am 99% certain that when I originally built the
database I attributed a Primary Key to this field but this is now removed
(either I have removed it, another user has removed it, the program has
removed it or it was not there in the first place!).

The records with the zero JobID entry also have a peculiar character in some
of the fields which is a series of vertical rectangles.

I assume that these two records are the key to my problem. However I can't
delete these records. If I try to delete I am presented with the message
'The search key was not found in any record'

Frankly, I stumped! However I need a solution soon because there is now a
growing backlog of data which needs inputting.

Any response will be greatly appreciated.

Original question
I have a database which I have been using for some 10 months or so. In the
last couple of days there have been search and closing problems both when
using forms or the data tables. If I perform a search using a form the
results don't show any record details and I get this message 'This action
will reset the current code in break mode. Do you want to stop running the
code?.....' This also happens in a tables but only after the result has
been sitting on the desktop for a while.

The program will then not close. I tried running 'compact and repair' but
this has not helped. Any suggestions?

 

[Arvin Meyer [MVP]]

First, always work on a copy of the database. Working on the original may
make it impossible for a repair service to fix it.

Download a copy of JetComp.exe:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

Try backing up your forms as text with the undocumented SaveAsText
LoadFromText functions:

http://www.datastrat.com/Code/DocDatabase.txt

Also have a look at the Microsoft KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;209137

Then have a look at Tony Toews' Access Corruption FAQ at:

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

for some suggestions. Unfortunately, some corruption cannot be fixed - you
may need to create a new database, import what can be salvaged, and recreate
the rest.

Although it's a paid service, Peter Miller does an outstanding job of saving
corrupt databases. Try this URL:

http://www.pksolutions.com

 

[Valentín Playá]

I remember a similar problem with Access 2000 I believe, and it was a
known problem. I have seen this problem in a few years but I think
Repair solved it, your case is worse.

You may try to use a query to copy the data to another table, or
export the table to Excel and import again, or import the table in new
database.

If posible work with Access 2003 in the FE and specially in the BE and
with 2003 format. If you have to work with 2000 update the Access in
all sites.

Regards,

Valentin Playa
Sonotronic S.A.
Madrid, Spain
************************************************************************************

 

[Larry Linson]

I recently posted a question (see below) which unfortunately
nobody seemed to be able to help me with.

If it had a Subject no more descriptive than "problem", it likely does not
mean "nobody could help" but that nobody who could help had time/energy to
open and read the post to see if it was a topic on which they could help or
one in which they had an interest. Many of the best potential responders are
also the busiest people, and have to rely on the Subject line to decide
whether to open and read a post.

For other good suggestions on effective use of newsroups, see
http://www.mvps.org/access/netiquette.htm.

Larry Linson
Microsoft Office Access MVP




Further to this question I have noticed that my

 

[freelancer]

Sorry Larry, my previous message was entitled 'Current Code in Break Mode'
which is a reference to the message I am receiving when trying to close the
dbase down. I assumed that user are reading this and thinking 'Red Alert,
avoid at all costs...' and so I have tried to prick users curiosity by using
an unusual title. I realise how busy people are and I know that a lot of
time and effort goes into the maintenance of these newsgroups. I have cause
to use the newsgroups frequently and I am very grateful for all responses.