Re: Pound sign in Access generates an error

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Steve Schapel (schapel_at_mvps.org.ns)
Date: 12/10/04 

Date: Sat, 11 Dec 2004 06:45:48 +1300

Gaby,

This sort of thing is normally a symptom of data corruption. It sounds
like this is happening frequently, so you will need to investigate the
cause. I was not able to reproduce the problem by simply inserting
"#Error" into a table, memo data type or otherwise. And there is no
restriction to the use of the # character in Access data.

There is some good information aout corruption at
http://www.granite.ab.ca/access/corruptmdbs.htm

The only way I know of to remove the corrupt record is to make a new
table, run an Append query from the existing table into the new table
for all records prior to the corrupt one, and then another append query
for all records following the corrupt one, and then delete the original
table and rename the new one to the old name. 

-- 
Steve Schapel, Microsoft Access MVP
Gaby wrote:
> We are having a Access Database (v 2003) which contains number, text and 
> memo field types. There is a record in the database that contains the string 
> "#Error" (without the quotes) for a memo field. This gives a problem when you 
> use this data in a DTS package for datatransformation. Opening the tabel and 
> selecting the "#Error" record results in the following error message:
> 
> The Microsoft Jet database engine stopped the process because you and 
> another user are attempting to change the same data at the same time.
> 
> Inserting the string "#Error" in a memo reproduces the error. We have't 
> found a way to remove the record containing the "#Error". The record 
> containing the "#Error" string is inserted in the Access database via a C# 
> program.
> 
> Does anyone know if there is a way to remove the records containing "#Error"?
> Is the usage of the #-sign in Access allowed in columns memo field?
> 
> Regards.

Relevant Pages

  • Re: Records corrupt in Access 2000+ but not Access 97
    ... Neither prevented my ability to corrupt the data. ... I'll remove record-level locking since this certainly corrupts records in my test situation. ... "Instead, use an unbound textbox for the memo field, and load the data from the recordsource into the unbound textbox in the OnCurrent event of the form, and then write to the field in the textbox's AfterUpdate event. ...
    (comp.databases.ms-access)
  • Re: Memo fields
    ... This and your description of the file indicated that the memo field has become ... corrupt. ... Try deleting that record and re-eintering it. ... the more of the same error message keeps popping up. ...
    (comp.databases.ms-access)
  • Re: Records corrupt in Access 2000+ but not Access 97
    ... I don't personally use the approach David suggests, so I will let him comment, or others who can speak from experience. ... Neither prevented my ability to corrupt the data. ... "Instead, use an unbound textbox for the memo field, and load the data from the recordsource into the unbound textbox in the OnCurrent event of the form, and then write to the field in the textbox's AfterUpdate event. ...
    (comp.databases.ms-access)
  • Re: Alternative to Access 2007 Memo Fields
    ... each disc of a season as a record. ... the memo field I get so far and then the memo field gets corrupted. ... I'm able to type everything in manually with no problem provided the memo field isn't corrupt. ... Or no one has the balls to admit that it is a bug. ...
    (microsoft.public.access.forms)
  • Pound sign in Access generates an error
    ... "#Error" for a memo field. ... Inserting the string "#Error" in a memo reproduces the error. ... containing the "#Error" string is inserted in the Access database via a C# ...
    (microsoft.public.access.forms)