1 Beware of babies and bathwater 2 Memos can be very useful and to avoid them can be more effort than they're worth 3 There are some extremely good data recovery tools out there 4 Why not look to see what caused the problem. The corruption is a result, not a cause
S On Thu, Feb 9, 2012 at 9:50 AM, Kurt Wendt <kurtwe...@waitex.com> wrote: > So - here where I work - they have generally stayed away from using MEMO > Fields in the FoxPro system they have. This old guy that worked here for > YEARS - he would Insist that they not be used in the system. Well, he's > been gone for like 1.5 years by now. > > > > Well, recently - in 2 different client systems and for 2 different > purposes - I decided to use a Memo field in a DBF. And, now it seems I > may be regretting having done so. > > > > There has been one or more times with the one client - where there was a > problem - and it seems that the Memo file or data got corrupted. > > > > And - now the problem is worse. It seems this one DBF (or maybe it was > multiple ones - as it happened a day ago and I don't have the full > report from the client) - that the DBF or a progam had crashed. Now - > they figured it was an Index problem - and re-indexed the files - but, > no good. So - my QA Tech buddy (they do the direct client support) - he > copied these 3 DBF files to another data folder - re-created the CDX > files for each - and then tried running this report - and the report > Still crashed. > > > > In the end - I had him Download from the client's server this one DBF - > along with the attached FPT file - to see if I could make it crash here > in the office. And, sure enough - a slight manipulation would make VFP > crash (Error: Fatal Error: Exception Code=C0000005). The error > originally happened when I would copy multiple records out to a Temp > file (that was the code in this report program). So - when I did it here > - the same crash would happen. I think narrowed down which record caused > the problem - by copying only a SINGLE Record at a time out to a Temp > file (each temp file was concatenated with the Record # - so I could see > which record caused the problem). And that did work. Just now - I went > to that record - and just went to double-click on the Memo field - and > the Error occurred again. > > > > So - it seems its Definitely the Memo field that is causing the problem! > > > > Any advice? Should I re-write their systems to NOT use Memo fields??? > > > > Thanks, > > -K- > > > > Senior Developer > > Waitex Information System, Inc. > > P Save a tree. Don't print this e-mail unless it's really necessary. > > > > > > --- StripMime Report -- processed MIME parts --- > multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cag1nny_o9e8e06gzla88dzilfr7xbyxixfcitb6vbm8g+zs...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
