On 12/06/2013 04:22 PM, Dan Covill wrote:
Allen,
Gene W. has it right.
This is an old problem. When you have an index set, modifying a field
that's part of the index expression changes where the modified record
appears in the order. It's one way to generate an infinite loop!
It's not a bug, it's a logical conundrum. You can't put your pants on
without changing feet.
Dan
On 12/06/13 03:23 AM, Allen wrote:
Hi Foxgang
I had a disturbing problem with VFP9 SP2 on Win 7 today
I have a scan routine looking for matching records and amending or
deleting
them. It took several goes to sort out the records. I had a filter
and order
on.
Took filter off and placed the filter constraints in the scan.
Same
Took the order off and fine all dealt with
Bit worrying.
Al
Along this same line, using FPDos 2.6, is there a way to detect if a
field was changed? I reindex after every edit since the indexed
fields often need to be corrected in the edit process. Reindexing
takes about 20 seconds, so its a delay. If I new if an indexed field
was edited, I would only reindex in that circumstance. This editing,
of course is done in the 'edit' mode, or in a browse window. I
usually use browse to select the record, then sometimes I use 'edit'
as opposed to a series of @/say/read statements.
John
_______________________________________________
Post Messages to: [email protected]
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/[email protected]
** 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.
