He might dress like the 2 wild and crazy guys on SNL  LOL

Even the tech noticed the problem followed this guy, but we are not sure why?
Magnetic personality or user error

Marc


--------------------------------------------------
From: "Emmitt Dove" <[email protected]>
Sent: Friday, February 04, 2011 12:11 PM
To: "RBASE-L Mailing List" <[email protected]>
Subject: [RBASE-L] - Re: Data corruption in a Varchar

> Does he wear polyester?
> 
> I think you just answered your own question.
> 
> Emmitt Dove
> Converting Systems Architect
> Evergreen Packaging, Inc.
> [email protected]
> (203) 214-5683 m
> (203) 643-8022 o
> (203) 643-8086 f
> [email protected]
> 
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of MDRD
> Sent: Friday, February 04, 2011 12:34
> To: RBASE-L Mailing List
> Subject: [RBASE-L] - Re: Data corruption in a Varchar
> 
> Albert
> 
> Funny thing is this guy use to work at another office, they had the trouble 
> back then, then he moves to a new office and the problem followed him! 
> Maybe he has too much static?
> 
> Thanks
> Marc
> 
> 
> --------------------------------------------------
> From: "Albert Berry" <[email protected]>
> Sent: Friday, February 04, 2011 11:04 AM
> To: "RBASE-L Mailing List" <[email protected]>
> Subject: [RBASE-L] - Re: Data corruption in a Varchar
> 
>> Marc, it can be something weird that is causing the trouble. Some years 
>> ago, we had a client app that worked perfectly until it got to the back 
>> office, where strange things would happen. Whoever ran the lines for the 
>> data draped one over a fluorescent fixture. We moved the line, and the 
>> problems went away.
>>
>> That was a strange one, indeed.
>> Albert
>>
>> On 04/02/2011 6:56 AM, MD RD wrote:
>>> Thanks Albert
>>>
>>> I have an option on our start up RBA menu that does that, and I told them
> 
>>> to give it a try but count the rows before and after to see if they loose
> 
>>> anything.
>>>
>>> I have a dozen offices using this same App in the same area and none have
> 
>>> this problems, just this one office.  So, I know RBase is not at fault 
>>> but I can not figure out what this user may be doing wrong and if there 
>>> is something I need to change in my App to prevent them from doing this 
>>> again.
>>>
>>> Marc
>>>
>>
>> 
> 
>

Reply via email to