Well, get some of the files that throw the error and autopsy them. You said the line that creates the file uses COPY. Usually, there's a little more to the line than that. TYPE CSV, XLS, or XL5?
And the source of the data? It's likely a SQL-SELECT or similar command, and it probably includes some calculations. A division by zero or transform could cause an overflow condition (Not a Number) or a picture clause overflow. Try using IMPORT to read the file back in and see what you get. Open the file in a hex editor (there's one in Fox) to see what's in the file. On Fri, May 27, 2016 at 10:52 AM, Kurt Wendt <kurt_we...@globetax.com> wrote: > Agreed - last resort is to track this down in Prod. But, sadly - the team > can't seem to recreate the Bug - it just kinda Happens. So - even if I did > something in Dev - I could be wasting my time - trying things over and over - > and the error won't happen! > > I'm going to go chat with them now - and see if there isn't some way I can > TRY to make this error happen again. Will report back here with what I find... > > Regards, > Kurt Wendt > Senior Systems Analyst > > > Tel. +1-212-747-9100 > www.GlobeTax.com > > > -----Original Message----- > From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Ted Roche > Sent: Friday, May 27, 2016 10:38 AM > To: profoxt...@leafe.com > Subject: Re: A Strange Excel Data Problem... > > Well, rather than instrumenting the Production version, create one in > Development and attempt to reproduce the problem. If that doesn't work, > promote it to Testing and see if it can be reproduced there. > Only as a last resort do you want the Production version to be used to track > down a bug. > > > On Fri, May 27, 2016 at 10:34 AM, Kurt Wendt <kurt_we...@globetax.com> wrote: >> In the Bar at the top - it literally shows Just that - and nothing more - >> just: #NUM! >> >> The spreadsheet has no expressions when its generated - just values. >> >> I may have to try that output to a Memo field. Although, here its not so >> simple. Everything must be in Releases. And, each release is based upon >> these PIDs (I think it stands for Proj ID #'s) - then every change has to go >> thru QA Testing and then potentially UAT testing. Fun, fun indeed! >> >> Regards, >> Kurt Wendt >> Senior Systems Analyst >> >> >> Tel. +1-212-747-9100 >> www.GlobeTax.com >> >> >> -----Original Message----- >> From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of >> Ted Roche >> Sent: Friday, May 27, 2016 9:58 AM >> To: profoxt...@leafe.com >> Subject: Re: A Strange Excel Data Problem... >> >> Open one of the spreadsheets and click in a cell that says #NUM! -- >> literally, Not A Number. >> >> Look in the bar across the top and see what the expression in the cell is. >> >> You can add a little instrumentation to the application to capture what is >> requested and what is output -- memo fields are good for this, but remember >> to clean them out before the database gets too big (PACK MEMO). >> >> >> >> On Fri, May 27, 2016 at 9:44 AM, Kurt Wendt <kurt_we...@globetax.com> wrote: >>> So - here at my day job my main task is to support this one team of users. >>> And, they're job is the Most Time critical here in this co. As such, things >>> must always be done in a timely manner - and support of them is critical in >>> that they Can not have the system down at any point in time. >>> >>> Well - part of the system outputs an Excel file that must be sent to the >>> clients. There is a problem that they have had over time. It's kind of >>> intermittent. Although - yesterday it happened to Four of the users about >>> the same time. So - they were kinda freakin' out. >>> >>> Problem is - they can't generally replicate the problem. So - if they can't >>> give me instructions on how to re-create the problem, its Nearly impossible >>> to try and fix the problem. >>> >>> Anyway - here's the issue. In a number of Cells in the spreadsheet - it >>> contains the following as a value: #NUM! >>> >>> And - yeah - that's exactly what it looks like - and I just copied it right >>> from the cell. >>> >>> Has anyone seen this kind of problem before??? >>> >>> Lastly - we are using VFP9 - and the Excel file is created using the COPY >>> command. >>> >>> Also - did a Google search - and one hit was M$ and a help page - it >>> claimed: >>> Excel shows this error when a formula or function contains numeric >>> values that aren't valid. >>> >>> But - of course, its Straight data being exported - NO Formulas! >>> >>> Any input would be greatly appreciated. >>> >>> Regards, >>> Kurt Wendt >>> Senior Systems Analyst >>> [GlobeTax_SecondaryLogo_TwoColor_Lo]<https://www.globetax.com/> >>> One New York Plaza - 34th Floor >>> New York, NY 10004-1936, USA >>> Tel. +1-212-747-9100 >>> Direct +1-212-405-8246 >>> www.GlobeTax.com<https://www.globetax.com/> >>> >>> GlobeTax does not provide or offer, and this is not, tax, investment or >>> legal advice. This email and any attachments hereto is intended only for >>> use by the addressee(s) and may contain confidential information. If you >>> are not the intended recipient of this email, please immediately notify the >>> sender at +1-212-747-9100 and permanently delete the original and any >>> copies of this email. >>> >>> >>> >>> --- StripMime Report -- processed MIME parts --- multipart/related >>> multipart/alternative >>> text/plain (text body -- kept) >>> text/html >>> image/png >>> --- >>> [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cacw6n4v2awk055omo7ljs7sij0wmykutgnehqj-x5ezbomf...@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.
