Has anyone ever had experience with data moving from one record to another?
I have a form in which I'm using the FMS rich text control ("Total Access
Memo"). Several times when there has been an error (such as the user unable
to print, or other error), the user finds that data in one or two of the
rich text fields are actually data that had previously been saved in another
record. This has happened two or three times in the past few months. And,
while not a frequent problem, it is especially troubling when it happens.

I've checked the FMS web site, and haven't seen anything about this. And
their technical support is pretty rudimentary. Not much help there. So I was
wondering if anyone has ever experienced anything like this, either with or
without a rich text control.

I'm using an Access 2000 MDB with a SQL Server 7 back end, with ODBC linked
tables.

Thanks for any assistance!

Neil

Neil

I'm curious how the users might be able to enter data "in the wrong record".
Is there a chance they are working directly in the tables?

Given the frequency with which this happens, are you sure you want to work
out an automated solution? Would it be easier (i.e., less work) just to
clean it up periodically? Or to prevent it from happening in the first
place by how your users access the data?

--
Regards

Jeff Boyce
www.InformationFutures.net

Microsoft Office/Access MVP
http://mvp.support.microsoft.com/

Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

"Neil" nospam.net> wrote in message
news:7Tquj.11650$Ej5.10391@newssvr29.news.prodigy.net...

another?

"Jeff Boyce" msn.com-DISCARD_HYPHEN_TO_END> wrote in message
news:uQ964yvcIHA.4588@TK2MSFTNGP06.phx.gbl...

No, they don't enter data in the wrong record. The data already exists in
the record, but it's transferred after the error.

Consider: record 1 has for two fields: A = Pete and B = John.
Record 2 has for two fields: A = Joe and B = Tom

After the error record 1 is A = Joe and B = John
And Record 2 is A = Joe and B = Tom.

In other words, after the error, the data from another record is
transferred into the current record, replacing its data, in one or two
fields.

Neil

I haven't run across that issue before.

Have you tried searching on-line?

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

"Neil" nospam.net> wrote in message
news:%%pGuj.1264$Mh2.1120@nlpi069.nbdc.sbc.com...

"Jeff Boyce" nonsense.com> wrote in message
news:%%23PCEuuzcIHA.4312@TK2MSFTNGP03.phx.gbl...

Yes; couldn't find anything.

Neil

Let's hope one of the other newsgroup readers has run across this!

You may want to re-post, as folks sometimes don't follow down-thread to see
that an answer was not yet found...

Regards

Jeff Boyce
Microsoft Office/Access MVP

Neil wrote:

Does your SQL server table have a primary key defined or did you build a
local index for doing updates? What you are describing is exactly what can
happen if you define a local index for doing updates and choose a field or
combination of fields that are actually NOT unique in the table. Updates
end up affecting multiple rows on the server.

"Rick Brandt" hotmail.com> wrote in message
news:yg2vj.2981$tW.1807@nlpi070.nbdc.sbc.com...

Thanks for your reply, Gordon. But, unfortunately, there is no code that
updates these fields. They're simply bound controls, and are managed by the
control and the ODBC driver.

Furthermore, the fact that the contents of the control are replaced by the
content of a previously saved record in that control indicates that it can't
be user error. These controls hold multiple sentences. For the user to be
able to retype exactly what was in another record, after already typing what
was in there originally, would be extremely unlikely.

I have code that copies the entire content of the record to a separate
history table whenever the form AfterUpdate event is run. Looking at the
history table, I see exactly what the user is talking about. There will be
multiple entries with the correct paragraph of text in the field, and then,
boom!, all of a sudden, out of nowhere, the contents of the field is
replaced, character-for-character, with the contents of another record for
the same field. If the user had done this, they would have to, after typing
the paragraph in the first place, all of a sudden decide to replace it wit
the wrong paragraph of text, and then replicate that other record's text
perfectly. Extremely unlikely.

"Neil" nospam.net> wrote

With all due respect, since this is an ActiveX Control by FMS, why are you
not pursuing the issue with FMS? My experience has been that (if you are
following their license provisions) they are good about providing support
and assistance.

Larry Linson
Microsoft Office Access MVP