Greetings all,
Looking at Bertil's buglist, this only shows an Sql problem, which we don't
use. Also, there isn't an opportunity to redesign this without formatted
memos, so I'd rather not have that discussion here.

My question is, will the 'corrupted' value survive being copied to/from
the backup, or will it 'fix' itself (and/or become blank)?

Greetings all,

A client is receiving a strange error with a Formatted Memo field "Error
writing file - record not tagged". This also causes a long delay in my
app
trying to get the value - sometimes over 5 minutes, which causes the
client
to think it is locked & they restart the app (very bad!).

The workaround is to wipe out this problem value, which fixes the problem
for the one record.

I'm writing a generalized script to fix every value. The script copies
every
value to a memo variable then to a backup table, & sets the production
value
to blank. The table will then be closed, giving an 'empty' MB file. A
second
pass on the table then reverses this to restore all the values.

My question is, will the 'corrupted' value survive being copied to/from
the
backup, or will it 'fix' itself (and/or become blank)? I'm hoping for the
'fix' option. The MB files are a mystery to me, so I don't know if the
corruption
is in -how- the value is stored or is inherent in the value itself.

Looking at Bertil's buglist, this only shows an Sql problem, which we
don't
use. Also, there isn't an opportunity to redesign this without formatted
memos, so I'd rather not have that discussion here.

TIA,
Jim Moseley

Greetings all,

A client is receiving a strange error with a Formatted Memo field "Error
writing file - record not tagged". This also causes a long delay in my
app
trying to get the value - sometimes over 5 minutes, which causes the client
to think it is locked & they restart the app (very bad!).

The workaround is to wipe out this problem value, which fixes the problem
for the one record.

I'm writing a generalized script to fix every value. The script copies
every
value to a memo variable then to a backup table, & sets the production value
to blank. The table will then be closed, giving an 'empty' MB file. A
second
pass on the table then reverses this to restore all the values.

My question is, will the 'corrupted' value survive being copied to/from
the
backup, or will it 'fix' itself (and/or become blank)? I'm hoping for the
'fix' option. The MB files are a mystery to me, so I don't know if the
corruption
is in -how- the value is stored or is inherent in the value itself.

Looking at Bertil's buglist, this only shows an Sql problem, which we don't
use. Also, there isn't an opportunity to redesign this without formatted
memos, so I'd rather not have that discussion here.

TIA,
Jim Moseley

You talk about 'problem value' but don't identify what the
value is - that might be helpful to know.

Is the table damaged once the value has been assigned to the field?

Is this only happening on that one system?

Table Repair shows the table is fine, no corruption.

"record not tagged". Is that something you output from your application?
I've never seen that message from pdox. Course I've never used formatted
memos either.

On Thu, 5 Mar 2009 11:31:29 -0500, Jim Giner wrote:

"record not tagged". Is that something you output from your application?
I've never seen that message from pdox. Course I've never used formatted
memos either.

That's what struck me. Formatted memos are rtf internally, where each
paragraph is (must be?) surrounded by start tags and end tags. Maybe a
paragraph lacks its start tags or end tags. That at least makes sense of
the error message.

--
Jim Hargan

And my question is whether the data in these memo fields, or some of it,
is
from copy/paste from Internet pages or other applications.

A LOT of garbage, that the user can't see, is captured along with text when

doing copy/paste of text from Internet pages.

Tony,

And my question is whether the data in these memo fields, or some of it,
is
from copy/paste from Internet pages or other applications.
A LOT of garbage, that the user can't see, is captured along with text when

doing copy/paste of text from Internet pages.


Good guess.

Jim Moseley