Wal-Mart would do it completely different than K-Mart.   Very, Very 
frustrating. 


________________________________
 From: Dave Crozier <da...@flexipol.co.uk>
To: ProFox Email List <profox@leafe.com> 
Sent: Thursday, February 9, 2012 4:40 AM
Subject: RE: USAGE Of Memos, Stability & an Error!
 
Rick,
I assume that the comment "... every time there is a ungracefull shit down of 
the app" was unintentional, even though it does describe the event perfectly!!! 
*grin*

Yes, after many years working on Mainframe EDI systems in the 80's I just got 
totally p*ssed off with the constant changes in the specifications and the ways 
in which every customer ended up with bespoke systems. It seems to me that 
there are about 4 main players in EDI that control the strings, each using 
slightly different standards that really screw developers around.

You would think that after all this time a better set of universal standards 
could be developed.... however it probably isn't in a few company's financial 
interests that the standards are set.

Dave


-----Original Message-----
From: profox-boun...@leafe.com [mailto:profox-boun...@leafe.com] On Behalf Of 
Richard Quilhot
Sent: 08 February 2012 20:55
To: ProFox Email List
Subject: Re: USAGE Of Memos, Stability & an Error!

Unless you really need that kind of space for storing unformatted text, do the 
rewrite.
This will continue to happen every time there is a ungracefull shit down of the 
app.

Rick Q
quilh...@gmail.com




On Wed, Feb 8, 2012 at 3:50 PM, 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/1328815278.21821.yahoomail...@web125602.mail.ne1.yahoo.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.

Reply via email to