>>>>>>>>Hi
>>>>>>>>
>>>>>>>>I am getting this error message after the Seek command
>>>>>>>>run-time error 3251
>>>>>>>>
>>>>>>>>which means the operation is not supported by this provider.
>>>>>>>>
>>>>>>>>when I issue this code return not supported
>>>>>>>>
>>>>>>>>Private Sub Command1_Click()
>>>>>>>>If rstUnit.Supports(adIndex) Then
>>>>>>>> MsgBox "index supported"
>>>>>>>>Else
>>>>>>>> MsgBox "not "
>>>>>>>>End If
>>>>>>>>If rstUnit.Supports(adSeek) Then
>>>>>>>> MsgBox "seek support"
>>>>>>>>Else
>>>>>>>> MsgBox "not "
>>>>>>>>End If
>>>>>>>>End Sub
>>>>>>>>
>>>>>>>>
>>>>>>>>I am using "Microsoft.Jet.OLEDB.4.0" access 97, and VB6 with SP6
>>>>>>>>
>>>>>>>>anyone have any idea how to solve this.
>>>>>>>>
>>>>>>>>Thankx in advance
>>>>>>>
>>>>>>>Which version of ADO is in reference? BTW, VB6 is now at SP4 (not 6).
>>>>>>
>>>>>>You are right Eric for VB6 it's SP4, and SP6 for NT (Iwas thinking of NT :)) )
>>>>>>
>>>>>>the ADO version is 2.1, and I included also :
>>>>>>- Ms Activex Data objects (multi-dimentional) 2.5 library
>>>>>>- Ms Activex Data objects 2.5 library
>>>>>>
>>>>>>but still the same error :(
>>>>>>
>>>>>>any suggestions ?
>>>>>
>>>>>Set your CursorLocation to client side.
>>>>
>>>>It's "to client side" ..
>>>
>>>What is your connection string?
>>
>>
>>Option Explicit
>> Public myConn As ADODB.Connection
>> Public myDataPath, myDataSource1, myDataSource2 As String
>>
>>Public Sub main()
>> myDataPath = "D:\mysystems\res\data\res.mdb"
>> Set myConn = New ADODB.Connection
>> myDataSource1 = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" _
>> & myDataPath & ";Persist Security Info=False"
>>
>> With myConn
>> .ConnectionString = myDataSource1
>> .Open
>> End With
>>
>> MDIfrmMainMenu.Show
>>End Sub
>>
>>Then the record set is :
>>
>>With rstUnit
>> .Index = "untno1"
>> .CursorLocation = adUseClient
>> .Open "unit", myConn, adOpenKeyset, adLockPessimistic, adCmdTableDirect
>>End With
>>
>>This is the seek syntax:
>>
>>rstUnit.Seek Array(20), adSeekFirstEQ
>
>It seams that the Seek method is only available for Access 2000. See http://support.microsoft.com/support/kb/articles/Q243/4/65.ASP


Does it mean that no way to do it with Access 97 ?!