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

#deleted appears in memo field?

P: n/a
I have an A2K app that I deplyed a year ago in a multiuser environment
(only 3-4 users max). The users recently drew my attention to a very
odd thing:
For one of their records a "Comments" field now has the text
"#Deleted." They wanted to change it to input the proper comments but
when they try Access gives them a warning that you are about to delete
RECORDS and then - after they were forced to click "OK" - ALL the
records disappeared! This scared the hell out of the users (luckily I
have been telling them to back up the Dbase several times a day), but
they then found that when they closed and reopened the form (based on
one table) all the data was back - including the "#deleted" record.

I opened up the underlying table and tried to delete the "#deleted"
but it did the same thing.

Any ideas???

Thanks in advance!
-Gordo
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
"GordoBR" <go*****@earthlink.net> wrote in message
news:34**************************@posting.google.c om...
I have an A2K app that I deplyed a year ago in a multiuser environment
(only 3-4 users max). The users recently drew my attention to a very
odd thing:
For one of their records a "Comments" field now has the text
"#Deleted." They wanted to change it to input the proper comments but
when they try Access gives them a warning that you are about to delete
RECORDS and then - after they were forced to click "OK" - ALL the
records disappeared! This scared the hell out of the users (luckily I
have been telling them to back up the Dbase several times a day), but
they then found that when they closed and reopened the form (based on
one table) all the data was back - including the "#deleted" record.

I opened up the underlying table and tried to delete the "#deleted"
but it did the same thing.


The table is corrupt. IME, none of the usual methods will repair the table
either until/unless you delete that row first. Often the biggest problem with
corruption like this is finding the row with the problem because in this state
the file won't compact and you can't import the table into another file. If
you're lucky and that's the only row with the problem, you can delete it and
then compact/repair the file.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
Nov 12 '05 #2

P: n/a
I had the same problem and just decompiled the database. The #Deleted
changed to the string XXXXXXX.
On Thu, 22 Jan 2004 15:40:06 -0600, "Rick Brandt"
<ri*********@hotmail.com> wrote:
"GordoBR" <go*****@earthlink.net> wrote in message
news:34**************************@posting.google. com...
I have an A2K app that I deplyed a year ago in a multiuser environment
(only 3-4 users max). The users recently drew my attention to a very
odd thing:
For one of their records a "Comments" field now has the text
"#Deleted." They wanted to change it to input the proper comments but
when they try Access gives them a warning that you are about to delete
RECORDS and then - after they were forced to click "OK" - ALL the
records disappeared! This scared the hell out of the users (luckily I
have been telling them to back up the Dbase several times a day), but
they then found that when they closed and reopened the form (based on
one table) all the data was back - including the "#deleted" record.

I opened up the underlying table and tried to delete the "#deleted"
but it did the same thing.


The table is corrupt. IME, none of the usual methods will repair the table
either until/unless you delete that row first. Often the biggest problem with
corruption like this is finding the row with the problem because in this state
the file won't compact and you can't import the table into another file. If
you're lucky and that's the only row with the problem, you can delete it and
then compact/repair the file.


Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.