Data Access Application Block with C#

[SAL]

Hi,

I have Microsoft Enterprise Library 2005 installed on my local system. I'm
developing in C# using Visual Studio 2003 IDE with framework 1.1.

I am automating a process that will use a DLL assembly I am developing. I
am going to use the data Access Application Block for data access in my DLL
assembly, and a Windows Service will execute the DLL on a set schedule. To
make this happen I will add the Common, Configuration, and Data projects to
my DLL assembly project.

My question is, how would I handle the SQL Server and Jet OLEDB database
Instances? The reason for Jet OLEDB, is my process will open an Excel
spreadsheet, read the data, then insert that data into a SQL Server database
table. However, I am fairly new to the Microsoft Enterprise Library 2005,
and it appears that Microsoft only provided SQL Server and Oracle access with
this reusable code.

Just an FYI, I keep my question short for simplicity, but there is more
going on in my DLL assembly that pushing data to SQL Server otherwise I would
have used DTS.

Thanks,

[sloan]

This is the 1.1 solution, but will get you down the right path.

//OLEDB
http://www.gotdotnet.com/Community/U...1-3781DF71DCDD

Adding it to the project was easier..since there are some private methods
need to be made public to have it outside the assembly.


"SAL" <SA*@discussion s.microsoft.com wrote in message
news:05******** *************** ***********@mic rosoft.com...

Hi,

I have Microsoft Enterprise Library 2005 installed on my local system. I'm
developing in C# using Visual Studio 2003 IDE with framework 1.1.

I am automating a process that will use a DLL assembly I am developing. I
am going to use the data Access Application Block for data access in my

DLL

assembly, and a Windows Service will execute the DLL on a set schedule.

To

make this happen I will add the Common, Configuration, and Data projects

to

my DLL assembly project.

My question is, how would I handle the SQL Server and Jet OLEDB database
Instances? The reason for Jet OLEDB, is my process will open an Excel
spreadsheet, read the data, then insert that data into a SQL Server

database

table. However, I am fairly new to the Microsoft Enterprise Library 2005,
and it appears that Microsoft only provided SQL Server and Oracle access

with

this reusable code.

Just an FYI, I keep my question short for simplicity, but there is more
going on in my DLL assembly that pushing data to SQL Server otherwise I

would

have used DTS.

Thanks,

[SAL]

Thanks. It does work in Visual Studio 2003 just fine.

For those interested in this, here's some additional important info from the
original author:
(http://www.geekswithblogs.net/cbreis.../03/38945.aspx)

Also, to make it work with Visual Studio 2003:

1. Create a new folder called OLEDB in C:\Program Files\Microsoft
Enterprise Library June 2005\src\Data\

2. Extract the contents from the download at gotdotnet link

3. Find the folder called Tests, and copy the entire Tests folder to the
OLEDB folder you created

4. Do the same for the files called OleDbCommandWra pper.cs & and
OleDbDatabase.c s

Just include it with you Data project so the next time you add the Data
project to your project you will have it.

Thanks again sloan.

"sloan" wrote:

This is the 1.1 solution, but will get you down the right path.

//OLEDB
http://www.gotdotnet.com/Community/U...1-3781DF71DCDD

Adding it to the project was easier..since there are some private methods
need to be made public to have it outside the assembly.


"SAL" <SA*@discussion s.microsoft.com wrote in message
news:05******** *************** ***********@mic rosoft.com...

Hi,

I have Microsoft Enterprise Library 2005 installed on my local system. I'm
developing in C# using Visual Studio 2003 IDE with framework 1.1.

I am automating a process that will use a DLL assembly I am developing. I
am going to use the data Access Application Block for data access in my

DLL

assembly, and a Windows Service will execute the DLL on a set schedule.

To

make this happen I will add the Common, Configuration, and Data projects

to

my DLL assembly project.

My question is, how would I handle the SQL Server and Jet OLEDB database
Instances? The reason for Jet OLEDB, is my process will open an Excel
spreadsheet, read the data, then insert that data into a SQL Server

database

table. However, I am fairly new to the Microsoft Enterprise Library 2005,
and it appears that Microsoft only provided SQL Server and Oracle access

with

this reusable code.

Just an FYI, I keep my question short for simplicity, but there is more
going on in my DLL assembly that pushing data to SQL Server otherwise I

would

have used DTS.

Thanks,

[sloan]

And here is the list of connection strings. (dataConfigurat ion.config file)
for Excel , Access, and TextFile:

<instances>
<instance name="pubsAcces sInstance" type="OleDB"
connectionStrin g="pubsAccessCo nnectionString" />

<instance name="pubsExcel Instance" type="OleDB"
connectionStrin g="pubsExcelCon nectionString" />

<instance name="textFileI nstance" type="OleDB"
connectionStrin g="textFileConn ectionString" />
</instances>
<connectionStri ngs>

<connectionStri ng name="pubsAcces sConnectionStri ng">
<parameters>
<parameter name="Provider" value="Microsof t.Jet.OLEDB.4.0 "
isSensitive="fa lse" />
<parameter name="Data Source"
value="c:\Acces sDatabaseCopy\p ubs2000.mdb" isSensitive="tr ue" />
</parameters>
</connectionStrin g>

<connectionStri ng name="pubsExcel ConnectionStrin g">
<parameters>
<parameter name="Provider" value="Microsof t.Jet.OLEDB.4.0 "
isSensitive="fa lse" />
<parameter name="Data Source" value="C:\Excel PubsCopy\pubs.x ls"
isSensitive="fa lse" />
<parameter name="Extended Properties" value="'Excel
8.0;HDR=Yes;IME X=1'" isSensitive="fa lse" />
</parameters>
</connectionStrin g>

<connectionStri ng name="textFileC onnectionString ">
<parameters>
<parameter name="Provider" value="Microsof t.Jet.OLEDB.4.0 "
isSensitive="fa lse" />
<!--
Notice the Data Source of a textfile is the DIRECTORY, not the full
path/filename
The Select statement looks like:
"Select * from mytextfile.txt"
-->
<!--
<parameter name="Data Source"
value="C:\Inetp ub\wwwroot\DotN etAssemblies\Gr anadaCoder\Appl ications\BulkDa t
aTransferExampl e\TextFilePubsE quiv\" isSensitive="fa lse" />
-->
<parameter name="Data Source" value="..\..\Te xtFilePubsEquiv \"
isSensitive="fa lse" />
<parameter name="Extended Properties"
value="'text;HD R=YES;FMT=Delim ited'" isSensitive="fa lse" />
</parameters>
</connectionStrin g>

</connectionStrin gs>


"SAL" <SA*@discussion s.microsoft.com wrote in message
news:87******** *************** ***********@mic rosoft.com...

Thanks. It does work in Visual Studio 2003 just fine.

For those interested in this, here's some additional important info from

the

original author:
(http://www.geekswithblogs.net/cbreis.../03/38945.aspx)

Also, to make it work with Visual Studio 2003:

1. Create a new folder called OLEDB in C:\Program Files\Microsoft
Enterprise Library June 2005\src\Data\

2. Extract the contents from the download at gotdotnet link

3. Find the folder called Tests, and copy the entire Tests folder to the
OLEDB folder you created

4. Do the same for the files called OleDbCommandWra pper.cs & and
OleDbDatabase.c s

Just include it with you Data project so the next time you add the Data
project to your project you will have it.

Thanks again sloan.

"sloan" wrote:

This is the 1.1 solution, but will get you down the right path.

//OLEDB

http://www.gotdotnet.com/Community/U...1-3781DF71DCDD

Adding it to the project was easier..since there are some private

methods

need to be made public to have it outside the assembly.


"SAL" <SA*@discussion s.microsoft.com wrote in message
news:05******** *************** ***********@mic rosoft.com...

Hi,
>
I have Microsoft Enterprise Library 2005 installed on my local system.

I'm

developing in C# using Visual Studio 2003 IDE with framework 1.1.
>
I am automating a process that will use a DLL assembly I am

developing. I

am going to use the data Access Application Block for data access in

my

DLL

assembly, and a Windows Service will execute the DLL on a set

schedule.

To

make this happen I will add the Common, Configuration, and Data

projects

to

my DLL assembly project.
>
My question is, how would I handle the SQL Server and Jet OLEDB

database

Instances? The reason for Jet OLEDB, is my process will open an Excel
spreadsheet, read the data, then insert that data into a SQL Server

database

table. However, I am fairly new to the Microsoft Enterprise Library

2005,

and it appears that Microsoft only provided SQL Server and Oracle

access

with

this reusable code.
>
Just an FYI, I keep my question short for simplicity, but there is

more

going on in my DLL assembly that pushing data to SQL Server otherwise

I

would

have used DTS.
>
Thanks,
>
>