>Hi Jim.
>
>Do you know if the OleDBCommandBuilder problems have been fixed in the VFP data driver in VFP9 ?
>(i.e If being used from within .Net)

I'm not sure know about this. We did fix a problem with the provider and the OleDBCommandBuilder prior to the public beta version. You should be able test in that version to see if the problem you refer to has been addressed.

>Also, can the VFP9 beta (or final product) be used to access VFP8 tables from within .Net

I don't see why not.


>
>Regards,
>
>Gerard
>
>
>>>Hi.
>>>I have downloaded and installed the latest VFPOLEDB driver, but am not sure if the latest one is in fact installed .
>>>
>>>Is there any way of checking what version I have.
>>>
>>>Documentation refers to two folders:
>>>..\Program Files\Common Files\Ssystem\OleDb
>>> which has a VFPOLDDB.DLL dated October 2003
>>>
>>>..\Program Files\Microsoft Visual Foxpro OleDB Provider
>>> which does not have any DLL's
>>>
>>>I understand from another thread that the VFPOLEDB was update Feb 2004
>>>
>>>Regards,
>>>
>>>Gerard
>>
>>Try this:
>>
>>

>>local lcPath as String, loConn as adodb.connection
>>
>>loConn = CREATEOBJECT('ADODB.Connection')
>>lcPath = _vfp.DefaultFilePath
>>loConn.ConnectionString = "Provider=VFPOLEDB.1;Data Source="+lcPath +";Mode=ReadWrite;Password='';Collating Sequence=MACHINE"
>>loConn.Open()
>>? loConn.Properties('Provider version').value
>>loConn.Close()
>>return
>>

>>
>>Latest released version is 8.00.0000.3117. The VFP9 public beta installs 9.0.0.1720