Connection to Paradox

Hello,
I am trying to connect to paradox database for the purpose of updating
the record(s) in DTS ActiveX Script Task.
I used the following connection string. But I get an error while
connection. I have "UMTest.db" and "UMTest.px" files in the
"C:\MYDBPath" in my local drive.
Set objRs = CreateObject("ADODB.RecordSet")
DB_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\MYDBPath;Extended Properties=Paradox 5.x;"
strSQL = " UPDATE UMTest SET Field1 = 1.222 WHERE Col1ID = '" & Value1
& "' AND Col2 = '" & Value2 & "'"
objRs.Open strSQL, DB_STRING
I get the following error.
Error Source: Microsoft Jet Database engine.
Error Description: No Value given for one or more required parameters.
Connection string looks alright to me. I don't know what is other
reason which is causing this error to happen.
Thanks.I don't do Paradox but to do any DML through Jet, you'd want to make sure
the table has a primary key defined. Also, you might want post this to a
paradox group.
http://www.thedbcommunity.com
-oj
"Yunus's Group" <yunusasmath@.gmail.com> wrote in message
news:1123266062.918633.324570@.g14g2000cwa.googlegroups.com...
> Hello,
> I am trying to connect to paradox database for the purpose of updating
> the record(s) in DTS ActiveX Script Task.
> I used the following connection string. But I get an error while
> connection. I have "UMTest.db" and "UMTest.px" files in the
> "C:\MYDBPath" in my local drive.
> Set objRs = CreateObject("ADODB.RecordSet")
> DB_STRING = "Provider=Microsoft.Jet.OLEDB.4.0;Data
> Source=C:\MYDBPath;Extended Properties=Paradox 5.x;"
> strSQL = " UPDATE UMTest SET Field1 = 1.222 WHERE Col1ID = '" & Value1
> & "' AND Col2 = '" & Value2 & "'"
> objRs.Open strSQL, DB_STRING
> I get the following error.
> Error Source: Microsoft Jet Database engine.
> Error Description: No Value given for one or more required parameters.
> Connection string looks alright to me. I don't know what is other
> reason which is causing this error to happen.
> Thanks.
>|||First, are you sure that's it's bombing out on your connection? If
you've verified this (try setting your strSQL to "SELECT 1" and see if
it still bombs out), then you may need to update your Paradox driver.
I've had to interface with a Paradox db before, and nothing worked
until we got a new driver for it installed on the SQL Server.
Since we were simply extracting data from Paradox during a batch
process, we ultimately ended up buying a copy of Paradox, and doing a
limited install on the SQL Server (basically drivers only).
HTH,
Stu