Marc,

I once had this happen to me,  without sounding like Razzak, make sure everyone 
is using the same version of RBase... My issue was solved once I found a user 
that had a version that was 2 releases back from myself and everyone else. (The 
user was afraid to let my update script run thinking it was a virus.)

Frank Taylor - Information Technology Administrator
F.J. O'Hara & Sons,  Inc - Araho Transfer Inc.
Boston, MA - Rockland, ME - Miami, FL
Direct Dial - 617-790-3093
email: 
[email protected]<http://mail.whitewolftechnologies.com/cgi-bin/compose.exe?id=01ef7f9322f8a76400dacb6a1fe342bb5a7&new=&xsl=compose.xsl&[email protected]>

From: [email protected] [mailto:[email protected]] On Behalf Of MDRD
Sent: Monday, July 26, 2010 12:54 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Data corruption

Hi

I have 2 offices that are having data corruption in the same Table.  This Table 
has a Varchar in it if that makes
any difference.  Both offices have good network techs looking into the problem 
but so far have not found any
problems.

One of these offices has been using this same Form / Table for over a year 
without any corruption, then I sent them
an update with minor changes.  So of course it appears there is something in my 
updated Form / EEPs' that may
be causing the problem but I can not think of anything that would cause a 
problem.

Is it possible I am doing something wrong in a EEP that is causing this 
corruption?  It seems random, 1x a week or so
and they use this same Form / Table daily.  Most of the time they use this form 
a workstation and this is the same
Form / Table that started that Slow Computer thread.

any suggestions appreciated
Thanks Marc




_______________________________________________________________________
This Email has been scanned for all viruses by PAETEC Email Scanning Services, 
utilizing MessageLabs proprietary SkyScan infrastructure. If you need 
assistance, please contact the Systems Administrator, Frank Taylor at 
[email protected] - 617-790-3093.
** REMEMBER NEVER OPEN AN ATTACHMENT UNLESS YOU ARE SURE OF IT'S CONTENT AND 
SENDER **
_______________________________________________________________________

Reply via email to