>>>-snip-
>>>>>
>>>>>W2K & ME come with MDAC 2.5, which already include the driver. You mention the MSJET, are you using Fox 2.x type tables?
>>>>
>>>>Yes, my program uses tables created by a legacy system using 2.x tables.
>>>
>>>And are you opening these files with DAO or ADO?
>>>
>>>If you are using ADO and the Jet provider then I don't think you need the VFP ODBC driver, just MDAC (and probably the Jet engine if you are using DAO).
>>
>>I'm using ADO:
>>
>>";SourceType=DBC;Exclusive=No;BackgroundFetch=Yes;Collate=Machine;Null=Yes;Deleted=YES;"
>> cConnectString = "DSN=Visual FoxPro Database;UID=;PWD=;SourceDB=" + strDatabasePath + cConnectStringEnd
>
>OK, so you are using the VFP ODBC driver. But does that work on 2.x tables? I don't think there was the concept of a DBC on Fox 2.x. To open free tables change the sourcetype to DBF and specify only a directory path on sourcedb.
>
>Also if you don't want to retrieve deleted records set Deleted=No.

You are correct. The app works great with this and I don't recieve the infamious "Unable to find installable ISAM" the VFP ODBC driver is functioning swell with this connection string. The problem arises on the client machine that has mdac 2.6 installed. I'm using windows installer and it doesn't seem to have a choice in MDAC flavors...

TIA