Nope, not accusing you of anything. Once I saw parts of your code that will not work for me, I quit examining your code. Compared to most code I see posted, yours looks a lot like plain jane FP code, so with a little time I could probably modify it to work in FP 2.6.
Sometimes when I see VFP...
OK, Mark, this code fixes the deficiency you noted. I also swatted two bugs that I found.
**********
*
* Get list of good, missing, or duplicate numbers within any range
* Lists number of duplicates found in test range, but not locations.
*
* = NUMGAPS(qTableName, qFieldName...
If you are talking to me, I DID answer some of your questions, but only those that I could answer. Useless trying to answer questions that I have not looked into. And no point in digging deeper than I needed to dig to determine that your code would not fly in plain Jane Foxpro.
I expanded and turned this into the function NUMGAPS() that I can now use myself, although I did not address the array length issue nor did I address decimal and scientific notation issues.
**********
*
* Get list of good, missing, or duplicate numbers within any range
*
* =...
Two nit picking things pop out. Did not dig further.
I (Integer) is not a field option
Dot notation
As for the array length, I was unaware of that since it has never bitten me, but the solution is simple, do a smaller chunk at a time. In this case an array is not likely to ever come close to...
Since it appears that none of the proposed solutions will work in plain Jane FoxPro, I came up with this which should work in all versions. Quick and dirty so likely can be improved upon. Tweek to fit your parameters.
Assumes your table is named "invoices" and the field is named "invnum"...
Whether you stay with FPD2.6 or upgrade to VFP, you have a lot of years left to use that "dead horse." And either way that dead horse will continue to prove that it is one of the most useful and easiest to use programs ever designed for managing relational databases.
$50,000 to move to a new...
Maybe he cannot upgrade.
Or maybe why fix that which is not broken?
I still use FoxPro 2.6b for the Mac because the ONLY VFP for the Mac is VFP 3.0 WHICH IS TOO BUGGY TO USE.
Ok, until I figure out why ESC is acting "erratically" in my code, I am going to use the CHR(1) method to CANCEL edits. Regardless, this change (a huge improvement) solves many of the problems I have been having with canceling edits. At least now my code is not likely to break when editing it. I...
Ok, did not know about SETting ESCAPE OFF. Will try that.
I saw about property in the Hacker's Guide, but so far as I know, there is no PROPERTY function in FPM 2.6b.
Thanks for posting that - It elegantly solves a problem I have had for decades - Now I can throw away my clunky solution.
However, it does not tell me where to and how to add the escape code to the buffer without causing an *** INTERRUPTED *** program error.
But, if I stuff the buffer with...
Depends a lot on what system you are using. My gut feeling is that as long as you do not use your computer for CRITICAL information, INCLUDING WHEN YOU ARE OFFLINE, that you should be ok.
I quit using anti-virus years ago because every one I tried would choke all of my computers, often to the...
So, exactly how are you displaying the data now? Numeric fields directly from your numeric data (with the resulting anomalies)? Text fields with manipulated data from your numeric data (with no anomalies)? How many screens display this data? Can you change the screens? Are you looking to create...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.