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.comhttps://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 ---
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_Wendt@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.comhttps://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]
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-bounces@leafe.com] On Behalf Of Ted Roche Sent: Friday, May 27, 2016 9:58 AM To: profoxtech@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_Wendt@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.comhttps://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]
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_Wendt@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-bounces@leafe.com] On Behalf Of Ted Roche Sent: Friday, May 27, 2016 9:58 AM To: profoxtech@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_Wendt@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.comhttps://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]
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-bounces@leafe.com] On Behalf Of Ted Roche Sent: Friday, May 27, 2016 10:38 AM To: profoxtech@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_Wendt@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-bounces@leafe.com] On Behalf Of Ted Roche Sent: Friday, May 27, 2016 9:58 AM To: profoxtech@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_Wendt@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.comhttps://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]
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_Wendt@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-bounces@leafe.com] On Behalf Of Ted Roche Sent: Friday, May 27, 2016 10:38 AM To: profoxtech@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_Wendt@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-bounces@leafe.com] On Behalf Of Ted Roche Sent: Friday, May 27, 2016 9:58 AM To: profoxtech@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_Wendt@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.comhttps://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]
On 27/05/2016 14:44, Kurt Wendt 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.
If the excel file is created using the copy command put a line before the copy to copy to a dbf for your use. You can then play with this file to try to copy to excel to reproduce the error. I've seen this kind of thing with say C(1) fields that have numbers in. After you copy to excel, if you try to sum the number it won't work. If you do the copy above you can look at the structure of the field that gives #NUM to check.
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
*#NUM!*
This error occurs if you supply a non valid number to a function argument. E.g, using a negative number when a positive is needed. Or, using a $, % symbol with the number.
This error can be masked so long as you are aware of the reason why. Again, use the Error.Type function as shown in #DIV/0!
On Fri, May 27, 2016 at 8:44 AM, Kurt Wendt Kurt_Wendt@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.comhttps://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]
They are purely #'s that get exported - so, no symbols involved.
Also - what is the ' Error.Type function ' you speak of?
As for Masking - nope, in this case - I really do NOT know the reason Why its occurring... :-(
Regards, Kurt Wendt Senior Systems Analyst
Tel. +1-212-747-9100 www.GlobeTax.com
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Stephen Russell Sent: Friday, May 27, 2016 12:55 PM To: profoxtech@leafe.com Subject: Re: A Strange Excel Data Problem...
*#NUM!*
This error occurs if you supply a non valid number to a function argument. E.g, using a negative number when a positive is needed. Or, using a $, % symbol with the number.
This error can be masked so long as you are aware of the reason why. Again, use the Error.Type function as shown in #DIV/0!
On Fri, May 27, 2016 at 8:44 AM, Kurt Wendt Kurt_Wendt@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.comhttps://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]
I have a form where in the Form Designer I set MaxWidth = 1400 and Width = 1400. I have the options in VFP IDE options set to "Max Design Area" = 1600 X 1200.
However, every time I open the form in the Form Designer, it resets the Width property to 1024.
How can I force VFP to keep the width at the 1400 value so I do not have to reset it each time I open the form to edit.
*Matt Slay*, President Jordan Machine Co. 355 Clow Lane PO Box 170339 Birmingham, AL 35217 Ph: 205-849-5050 Fx: 205-849-5075 mattslay@jordanmachine.com mailto:mattslay@jordanmachine.com http://www.JordanMachine.com
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
I would think this lives in foxuser? What happens if you clear out your foxuser table?
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Matt Slay Sent: Tuesday, June 21, 2016 10:02 AM To: profoxtech@leafe.com Subject: Form Width property won't persist...
I have a form where in the Form Designer I set MaxWidth = 1400 and Width = 1400. I have the options in VFP IDE options set to "Max Design Area" = 1600 X 1200.
However, every time I open the form in the Form Designer, it resets the Width property to 1024.
How can I force VFP to keep the width at the 1400 value so I do not have to reset it each time I open the form to edit.
*Matt Slay*, President Jordan Machine Co.
Hi, What happens if you set the width and other sizings in the init of the form? Does it still shrink to 1024? If so there should be something else going, GoFish4 '1024' or debugger? Regards, Koen P.S. I did not even try to be funny with my first suggestion
2016-06-21 16:02 GMT+02:00 Matt Slay mattslay@jordanmachine.com:
I have a form where in the Form Designer I set MaxWidth = 1400 and Width = 1400. I have the options in VFP IDE options set to "Max Design Area" = 1600 X 1200.
However, every time I open the form in the Form Designer, it resets the Width property to 1024.
How can I force VFP to keep the width at the 1400 value so I do not have to reset it each time I open the form to edit.
*Matt Slay*, President Jordan Machine Co. 355 Clow Lane PO Box 170339 Birmingham, AL 35217 Ph: 205-849-5050 Fx: 205-849-5075 mattslay@jordanmachine.com mailto:mattslay@jordanmachine.com http://www.JordanMachine.com
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
Hi Matt:
Occurs only with this form, or with others too?
Have you tryied with another form?
2016-06-21 16:02 GMT+02:00 Matt Slay mattslay@jordanmachine.com:
I have a form where in the Form Designer I set MaxWidth = 1400 and Width = 1400. I have the options in VFP IDE options set to "Max Design Area" = 1600 X 1200.
However, every time I open the form in the Form Designer, it resets the Width property to 1024.
How can I force VFP to keep the width at the 1400 value so I do not have to reset it each time I open the form to edit.
*Matt Slay*, President Jordan Machine Co. 355 Clow Lane PO Box 170339 Birmingham, AL 35217 Ph: 205-849-5050 Fx: 205-849-5075 mattslay@jordanmachine.com mailto:mattslay@jordanmachine.com http://www.JordanMachine.com
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]
On 21/06/2016 15:02, Matt Slay wrote:
I have a form where in the Form Designer I set MaxWidth = 1400 and Width = 1400. I have the options in VFP IDE options set to "Max Design Area" = 1600 X 1200.
However, every time I open the form in the Form Designer, it resets the Width property to 1024.
How can I force VFP to keep the width at the 1400 value so I do not have to reset it each time I open the form to edit.
Try setting the maximum design area to "None". On mine it shows 1600x1200 as the largest size but it's the 1400 > 1200 that is causing the problem.
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
I tried that. No luck... I even restarted VFP to reset everything, but still get the same result.
*Matt Slay*, President Jordan Machine Co. 355 Clow Lane PO Box 170339 Birmingham, AL 35217 Ph: 205-849-5050 Fx: 205-849-5075 mattslay@jordanmachine.com mailto:mattslay@jordanmachine.com http://www.JordanMachine.com
On 6/21/2016 9:37 AM, Peter Cushing wrote:
On 21/06/2016 15:02, Matt Slay wrote:
I have a form where in the Form Designer I set MaxWidth = 1400 and Width = 1400. I have the options in VFP IDE options set to "Max Design Area" = 1600 X 1200.
However, every time I open the form in the Form Designer, it resets the Width property to 1024.
How can I force VFP to keep the width at the 1400 value so I do not have to reset it each time I open the form to edit.
Try setting the maximum design area to "None". On mine it shows 1600x1200 as the largest size but it's the 1400 > 1200 that is causing the problem.
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email. www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715 London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
[excessive quoting removed by server]
Then if problem is only with this form and not other, probably has some corruption inside. Convert it to text (sc2) and back to bin. El 21/6/2016 16:55, "Matt Slay" mattslay@jordanmachine.com escribió:
I tried that. No luck... I even restarted VFP to reset everything, but still get the same result.
*Matt Slay*, President Jordan Machine Co. 355 Clow Lane PO Box 170339 Birmingham, AL 35217 Ph: 205-849-5050 Fx: 205-849-5075 mattslay@jordanmachine.com mailto:mattslay@jordanmachine.com http://www.JordanMachine.com
On 6/21/2016 9:37 AM, Peter Cushing wrote:
On 21/06/2016 15:02, Matt Slay wrote:
I have a form where in the Form Designer I set MaxWidth = 1400 and Width = 1400. I have the options in VFP IDE options set to "Max Design Area" = 1600 X 1200.
However, every time I open the form in the Form Designer, it resets the Width property to 1024.
How can I force VFP to keep the width at the 1400 value so I do not have to reset it each time I open the form to edit.
Try setting the maximum design area to "None". On mine it shows 1600x1200 as the largest size but it's the 1400 > 1200 that is causing the problem.
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email. www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715 London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
[excessive quoting removed by server]
/>>//Then if problem is only with this form and not other, probably has some//corruption inside./
Ah-hah... I've learned that forms based on the VFP base form class will retain their width setting.
It's only the forms in my app that are based on my form class that will not retain the Width value.
/ /
*Matt Slay*, President Jordan Machine Co. 355 Clow Lane PO Box 170339 Birmingham, AL 35217 Ph: 205-849-5050 Fx: 205-849-5075 mattslay@jordanmachine.com mailto:mattslay@jordanmachine.com http://www.JordanMachine.com
On 6/21/2016 9:59 AM, Fernando D. Bozzo wrote:
Then if problem is only with this form and not other, probably has some corruption inside. Convert it to text (sc2) and back to bin. El 21/6/2016 16:55, "Matt Slay" mattslay@jordanmachine.com escribió:
I tried that. No luck... I even restarted VFP to reset everything, but still get the same result.
*Matt Slay*, President Jordan Machine Co. 355 Clow Lane PO Box 170339 Birmingham, AL 35217 Ph: 205-849-5050 Fx: 205-849-5075 mattslay@jordanmachine.com mailto:mattslay@jordanmachine.com http://www.JordanMachine.com
On 6/21/2016 9:37 AM, Peter Cushing wrote:
On 21/06/2016 15:02, Matt Slay wrote:
I have a form where in the Form Designer I set MaxWidth = 1400 and Width = 1400. I have the options in VFP IDE options set to "Max Design Area" = 1600 X 1200.
However, every time I open the form in the Form Designer, it resets the Width property to 1024.
How can I force VFP to keep the width at the 1400 value so I do not have to reset it each time I open the form to edit.
Try setting the maximum design area to "None". On mine it shows 1600x1200 as the largest size but it's the 1400 > 1200 that is causing the problem.
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email. www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715 London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
[excessive quoting removed by server]
-
Fernando D. Bozzo -
Koen Piller -
Kurt Wendt -
Matt Slay -
Peter Cushing -
Richard Kaye -
Stephen Russell -
Ted Roche