Corruption Risk?

[Guest]

Looking for some advice in advance.."An ounce of prevention is worth more
than a pound of hamburger". (Or something like that).

I'm a temp contractor modifying a 16-user, 2002 Access database. They rely
heavily on a CO_CommentText field (Memo) which currently receives input from
various forms. A questionable (yet unlikely to change) practice is for them
to cut and paste their data straight from non-fixed sources such as Outlook
messages and emailed Excel Spreadsheets. Of course, this is causing carriage
return characters and spacings that make WingDings look intelligible.


I have two update queries that deal successfully with the removal of these
unnecessary characters but would like to know when to have them fire, i.e. a
command button for users, or perhaps during a form opening (concerned about
unnecessary delays with that one), an administrative action (no
administrators have exclusivity to the database due to working the same hours
as the rest of the users). I want to ensure that there is no likelihood of
corruption during the removal of these characters en mass while the users are
in the database.

Thanks.

 

[Brendan Reynolds]

I'd do it in the AfterUpdate event procedure of the text boxes ...

Private Sub TestMemo_AfterUpdate()

Me.TestMemo = Replace(Replace(Replace(Me.TestMemo, _
vbCr, Space$(1)), vbLf, Space$(1)), vbCrLf, Space$(1))

End Sub

 

[Guest]

Brilliant! Excellent advice. Thanks again!

I'd do it in the AfterUpdate event procedure of the text boxes ...

Private Sub TestMemo_AfterUpdate()

Me.TestMemo = Replace(Replace(Replace(Me.TestMemo, _
vbCr, Space$(1)), vbLf, Space$(1)), vbCrLf, Space$(1))

End Sub