In Biztalk 2002 we are performing a Database lookup functoid using Provider=
MSDASQL.1.  When I try to use the same provider in Biztalk 2004 system.data 
does not support it.  Any ideas?

[ Post a follow-up to this message ]

Try

provider=SQLOLEDB.1

"Ktz4" wrote:

> In Biztalk 2002 we are performing a Database lookup functoid using Provide
r=MSDASQL.1.  When I try to use the same provider in Biztalk 2004 system.dat
a does not support it.  Any ideas?
>

[ Post a follow-up to this message ]

I have tried the following and these are the results I get:

Provider=MSDASQL.1;Data Source = DataSourceName

The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not supp
ort the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net F
ramework Data Provider for ODBC (System.Data.Odbc).
-------------------------------------------------------------
Provider=ODBC;Data Source = DataSourceName

The 'ODBC' provider is not registered on the local machine.
-------------------------------------------------------------
Provider=SQLOLEDB.1;Data Source = DataSourceName

Invaild authorization specification
-------------------------------------------------------------               
                                                                            
                                                                            
The DSN is configured to us
e the Microsoft Access Driver (*.mdb).  Any ideas would be greatly appreciat
ed.




"Scott White" wrote:
[vbcol=seagreen]
> Try
>
> provider=SQLOLEDB.1
>
> "Ktz4" wrote:
> 

[ Post a follow-up to this message ]

Hi. Try with
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=<database>;Data Source=<db-server>

Replace the strings in brackets with something useful. The above
connectionstring is for integrated security and not username/password.

Jan Eliasen.

On Mon, 14 Jun 2004 12:39:01 -0700, "ktz4"
<ktz4@discussions.microsoft.com> wrote:

>I have tried the following and these are the results I get:
>
>Provider=MSDASQL.1;Data Source = DataSourceName
>
>The .Net Framework Data Provider for OLEDB (System.Data.OleDb) does not sup
port the Microsoft OLE DB Provider for ODBC Drivers (MSDASQL). Use the .Net 
Framework Data Provider for ODBC (System.Data.Odbc).
>-------------------------------------------------------------
>Provider=ODBC;Data Source = DataSourceName
>
>The 'ODBC' provider is not registered on the local machine.
>-------------------------------------------------------------
>Provider=SQLOLEDB.1;Data Source = DataSourceName
>
>Invaild authorization specification
>-------------------------------------------------------------                      
                                                                                    
                                                             The DSN is configured t
o u
se the Microsoft Access Driver (*.mdb).  Any ideas would be greatly appreciated.[vbcol=seagr
een]
>
>
>
>
>"Scott White" wrote:
> 

--
Jan Eliasen, representing himself and not the company he works for.

[ Post a follow-up to this message ]

This works great with SQL, but I'm trying to connect to a Microsoft Access d
atabase.  Any other ideas?

"Jan Eliasen" wrote:

> Hi. Try with
> Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security
> Info=False;Initial Catalog=<database>;Data Source=<db-server>
>
> Replace the strings in brackets with something useful. The above
> connectionstring is for integrated security and not username/password.
>
> Jan Eliasen.
>
> On Mon, 14 Jun 2004 12:39:01 -0700, "ktz4"
> <ktz4@discussions.microsoft.com> wrote:
> 
use the Microsoft Access Driver (*.mdb).  Any ideas would be greatly appreciated.[vbcol=seag
reen] 
>
> --
> Jan Eliasen, representing himself and not the company he works for.
>

[ Post a follow-up to this message ]

Hi

Well, try removing some part of the string I suggested?

For instance, try removing "Persist Security Info=False" or something.
See if that will work - perhaps one of the others.

Jan Eliasen

On Mon, 21 Jun 2004 11:26:01 -0700, "ktz4"
<ktz4@discussions.microsoft.com> wrote:
[vbcol=seagreen]
>This works great with SQL, but I'm trying to connect to a Microsoft Access 
database.  Any other ideas?
>
>"Jan Eliasen" wrote:
> 
o use the Microsoft Access Driver (*.mdb).  Any ideas would be greatly appreciated.[vbcol=se
agreen] 

--
Jan Eliasen, representing himself and not the company he works for.

[ Post a follow-up to this message ]

Thanks!  I finally got it with:  Provider=Microsoft.Jet.OLEDB.4.0;Data Sourc
e=C:\Directory\dbname.mdb;Persist Security Info=False

"Jan Eliasen" wrote:

> Hi
>
> Well, try removing some part of the string I suggested?
>
> For instance, try removing "Persist Security Info=False" or something.
> See if that will work - perhaps one of the others.
>
> Jan Eliasen
>
> On Mon, 21 Jun 2004 11:26:01 -0700, "ktz4"
> <ktz4@discussions.microsoft.com> wrote:
> 
to use the Microsoft Access Driver (*.mdb).  Any ideas would be greatly appreciated.[vbcol=s
eagreen] 
>
> --
> Jan Eliasen, representing himself and not the company he works for.
>

[ Post a follow-up to this message ]