We changed the code back just to be safe. Otherwise, the oledb driver has to be installed on every machine as well.


>I'd mark that section still as a worry point in the code: I've read warnings about sys(3055) making vfp slower.
>Not tested, but it should eat into memory. Also I think the ability to index a temp table/cursor at times of your discretion
>is useful - no idea when vfp will kick in rushmore by creating tmp indexes.
>
>Your previous solution would be the one I stay with, even if the code is less elegant.
>
>regards
>
>thomas
>
>>I just downloaded the vfp9 9.0 SP2 OLE DB provider, and surprisingly, it works :O)
>>
>>
>>>>You are correct. I just found this:
>>>>
>>>>There are also no hard-coded limits on the number of items in a SQL IN list. In versions prior to Visual FoxPro 9, SQL IN was mapped to the INLIST() function; that dependency has been removed. This change allows an increase in the number of arguments for IN and for better optimization. Visual FoxPro 9 stops evaluating expressions from the list as soon as the match is found. This is helpful if the IN condition is not Rushmore-optimized, as performance can be improved by placing the most-likely-to-match values at the beginning of the list. The total number of items is still indirectly limited by the SYS(3055) function, which controls buffer memory size, so the higher the setting, the more items are supported via IN. (See the Common Error Messages sidebar for more information.)
>>>>
>>>>from:
>>>>
>>>>http://www.vfpconversion.com/Article.aspx?quickid=0404022
>>>>
>>>>Thanks Naomi...
>>>
>>>You're welcome. I guess I read this info once as well. So, how we're going to solve the problem?