Well, the best test of the static issue would be to give him a wireless keyboard and mouse.
Emmitt Dove Converting Systems Architect Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: Friday, February 04, 2011 14:57 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Data corruption in a Varchar I agree. I'm leaning more toward some sequence of keystrokes that this guy likes to do. When I create a form, I lean toward what I think is a logical sequence of events. Sometimes, anothers logic is not the same as mine. Go somebody! (I haven't made up my mind yet) Jan -----Original Message----- From: Dennis McGrath <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Fri, 4 Feb 2011 13:52:59 -0600 Subject: [RBASE-L] - Re: Data corruption in a Varchar I haven’t experienced the static problems we used to have for a VERY long time. I think the keyboards/mice/computers are much better protected now. I don’t think that is where you problem lies. Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave Itasca IL 60143 630-980-8461 [email protected] _____ From: [email protected] [mailto: [email protected]] On Behalf Of Emmitt Dove Sent: Friday, February 04, 2011 1:28 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Data corruption in a Varchar Some people tend to accumulate or generate more static electricity than others, and clothing (especially polyester) in conjunction with the fabric on the chair or the carpet and the shoes being worn can all play a role in this. We had one person who was like this in our New Jersey plant years ago. No amount of grounding keyboards and anti-static mats on the floor seemed to help. So, all this time you’ve been searching for a software issue when in reality it is probably this simple. Emmitt Dove Converting Systems Architect Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto: [email protected]] On Behalf Of MDRD Sent: Friday, February 04, 2011 14:14 To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Data corruption in a Varchar 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 >>> >> >> > >
