Hey -- I worked around this, but I just saw the weirdest thing:
I am updating a conversion program taking data from an ancient system to a new one which is "going live" in the next couple of days. So -- I am doing a lot of SQL select's - then manipulating the data to match up with my new structures, and populating the new tables. So, get this: I am de-dupping the data, populating place_id values. Using old-fashioned Fox, I do the expedient thing and create a unique index on *just that value* spin through the table, and populate the new structures. Hmmm -- many people don't have places. Look through the cursor tables with the unique index on and -- some place_id's are not there! In the case I was looking at, there was #91 and #93, but #92 disappeared! Turn the index off, (or another one on): there's #92. <cue "Twilight Zone" music> Have you ever seen such a thing? Can't be corruption, all of these are SQL-built (nofilter) r/w cursors. Again, I don't need help -- I did it another way -- I am just perplexed what could cause such a strange behavior. Ken _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://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.
