|
|
Post by foxpropgmr on Jun 24, 2021 22:14:47 GMT 1
Right after that index command, type >>> set deleted on <enter>
Then browse
Should still show all the records. Mine just shows the first one
|
|
|
|
Post by Jos on Jun 25, 2021 18:45:34 GMT 1
Still the same results (615 records) with both versions.
Use WALT.DBF excl
Index on Deleted() tag Deleted
set deleted on
Jos
|
|
|
|
Post by foxpropgmr on Jun 25, 2021 23:04:57 GMT 1
ok .. I'll keep working on it
|
|
|
|
Post by Jos on Jun 26, 2021 5:30:29 GMT 1
Also with your data files:  Jos |
|
|
|
Post by foxpropgmr on Jun 26, 2021 10:49:34 GMT 1
I'm a little bewildered. Tested it on another machine ... got the same issue.
So let's start at square one. Are you using Foxprox.exe version 2.6a?
|
|
|
|
Post by foxpropgmr on Jun 26, 2021 10:53:47 GMT 1
|
|
|
|
Post by Jos on Jun 26, 2021 11:20:46 GMT 1
?  |
|
|
|
Post by foxpropgmr on Jun 26, 2021 11:40:14 GMT 1
Sent you 2.6a to test
|
|
|
|
Post by Jos on Jun 26, 2021 14:39:46 GMT 1
That didn't arrive yet.
If you sent it by email: If an attachment is something executable, the email is blocked.
I use wetransfer.com to send those.
Jos
|
|
|
|
Post by Jos on Jun 27, 2021 14:09:53 GMT 1
Shoot, my bad.
At testing your code fragment, before adding “set deleted on”, I apparently set a vDos switch to (temporary) disable optimizing FoxProX.
Didn’t reenable that, so from then on it just worked fine at my side since BROWSE only showing one record was caused by:
vDos identifies and substitutes a FoxProX core function comparing two memory blocks up to a given number of bytes. Whereas standard C functions like strncmp() and memcmp() are documented to return 0, >0 or <0 to reflect the result of the comparison, FoxProX explicitly tests for 0, 1 or -1 with this function. The >0 versus 1 was the culprit.
I changed the function to return what FoxProX expects, and will send you a corrected vDos.exe.
Jos
|
|
|
|
Post by foxpropgmr on Jun 27, 2021 16:41:30 GMT 1
And I looked at that too ... and it didn't ring a bell enough for me to stop and test it.
At least one of us did. lol
|
|
|
|
Post by foxpropgmr on Jun 28, 2021 1:00:05 GMT 1
Everything seems fine now. Thanks for your quick response.
Walt
|
|
