Updating FoxPro table using ADO
I have Foxpro tables that I'm trying to edit/add to but I keep getting an error "Current record does not support updating. This may be a limitation of the provider, or of the selected locktype."
It allows me to select records and read records, but does not allow edits or adds. I've tried all 4 Locktypes in combination with all 4 CusorTypes available, but keep getting the same error.
I'm using VB6 with and ADO connection to FoxPro 8.0. Any ideas on what I'm doing wrong? I've already checked the persmissions and have Full control set for the database and all the tables.
'-- Code
m_dbObjectDB.Mode = ADODB.ConnectModeEnum.adModeReadWrite
m_dbObjectDB.Open "Provider=VFPOLEDB.1;Data Source=c:\Mydatabase.dbc;SourceType=dbf;BackgroundFetch=Yes;Deleted=Yes;Mode=ReadWrite|Shar e Deny None;" _
& "Extended Properties="""";User ID="""";Password="""";Mask Password=False;" _
& "Cache Authentication=False;Encrypt Password=False;Collating Sequence=MACHINE"
m_rsObjectRS.ActiveConnection = m_dbObjectDB
m_rsObjectRS.Open "SELECT * FROM Customer", m_dbObjectDB, adOpenKeyset, adLockOptimistic, adCmdText
[1212 byte] By [
rocket] at [2007-11-19 1:44:31]
# 2 Re: Updating FoxPro table using ADO
A website I found with connection string examples, gave the following:
oConn.Open "Provider=vfpoledb;" & _
"Data Source=C:\vfp8\Samples\Data\myVFPDB.dbc;" & _
"Mode=ReadWrite|Share Deny None;" & _
"Collating Sequence=MACHINE;" & _
"Password=''"
The difference between it and yours is, that it specifies the Mode (ReadWrite etc). Have you tried your string with the mode added?
HTH
# 3 Re: Updating FoxPro table using ADO
I finally had a chance to try out the code above, but kept getting the same error. I had high hopes for that, but alas. Thank you for your input, and if anyone has a solution, or possible solution, by all means, feel free to post.
Thank you
# 6 Re: Updating FoxPro table using ADO
hello friends, I have the same problem, I can connect to the foxpro database but I cannot modify neither to add. the error that gives me is the same, I believe that the problem is with the Provider. was some of you able finally to solve the problem?
roilld at 2007-11-9 13:43:53 >
