Only when the indexes are bad. I get the same results with select statements flattening the data. Until I fix the index, or use NOOPTIMIZE on the select statement.
I've seen your behavior due to a problem with other code assigning the wrong parent key. HTH, Tracy -----Original Message----- From: MB Software Solutions General Account Sent: Friday, February 20, 2009 12:22 PM Grrrr! Our classic/legacy app is sometimes flaky in certain areas where we produce invoices for our parents. Sometimes we get a non-related kid on the invoice, and of course that's a bad thing! Investigating the code, it relies heavily on SET RELATION and I just recall that biting me years ago (1999-2000) with VFP6. Bugs that are consistent and reproducible are one thing, but bugs like this that happen "every now and a long then" are sure a PITA. I personally don't care for the SET RELATION style of coding, but hey, that's me. Anyone else ever have flaky behavior in a SET RELATION section of code? (I'm talking about VFP free tables on a LAN in a multi-user environment.) Ugh... _______________________________________________ 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/000601c9937f$39b654b0$ad22fe...@com ** 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.
