1) Wouldn't that be SET ENGINEBEHAVIOR 70 if you want old style VFP 7 SQL behavior (i.e. ambiguous results for non-aggregate columns not included in GROUP clause)?
2) I always wonder about this recommendation because if the table header is corrupted in a particular way, your users won't know about it until after they think that they've saved some new data that doesn't show up. Dave Crozier wrote: > Other possible settings to look at are: > > 1. Set ENGINEBEHAVIOR 80 -> makes SQL "group by" behaviour as per VFP7 > > 2. Set TableValidate 0 -> Removes the Table header check on open which > temporarily locks the table > > -- Richard Kaye Vice President Artfact/RFC Systems Voice: 617.219.1038 Fax: 617.219.1001 For the fastest response time, please send your support queries to: Technical Support - [EMAIL PROTECTED] Australian Support - [EMAIL PROTECTED] Internet Support - [EMAIL PROTECTED] All Other Requests - [EMAIL PROTECTED] --------------------------------------------------------- This message has been checked for viruses before sending. --------------------------------------------------------- _______________________________________________ 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.
