I am developing a desktop DB-application where 

the ADO.NET diskonnected datasets are quite

inconvenient.



Anybody knows any resources (articles ) that discusses

this?  Appropriate examples for using ADO.NET in

such applicatons?  E.g. doing Master-Detail forms

by fetching the child-rows when needed?



Thanks!

Olav

Have you considered MSDE?



-----Original Message-----

From: Olav Benum [mailto:wrox@b...]

Sent: Sunday, January 20, 2002 3:33 PM

To: ADO.NET

Subject: [ado_dotnet] Resources for local desktop databases



I am developing a desktop DB-application where

the ADO.NET diskonnected datasets are quite

inconvenient.



Anybody knows any resources (articles ) that discusses

this?  Appropriate examples for using ADO.NET in

such applicatons?  E.g. doing Master-Detail forms

by fetching the child-rows when needed?



Thanks!

Olav






$subst('Email.Unsub').

In article <137746@a..._dotnet>, willisj@m... says...

> 

> Have you considered MSDE?

I am currently using Access.  I Think MSDE is a kind of

light SQL Server?  I think that would be moving in the 

wrong direction for me.



I was thinking more of ways to use Access better, or something

"lighter".  I could perhaps use flat files or XML,so that I have

only on layer of database logic?  Or are there any ADO.NET oriented

database software?



Now with ADO.NET I am essentially taking a copy of most

of the data in my database, processing it, and writing it 

back.  This is not very efficient, it is also quite complex

because I have two layers with logic.



(My application should also be easy to deploy)



Thanks!

Olav

Hi Olav,

There are two issues here:



1. MSDE is SQL Server without a user interface.  You can address it via

ADO.NET just as you would SQL Server itself. Depending on which version

of Access you're using, you may already have MSDE. Access is basically a

user interface on top of a database engine, either "Jet" or "MSDE". It

includes a conversion utility for upscaling to SQL Server, supported by

MSDE.



2. As far as the disconnected database model is concerned, that's an

essential feature of ADO.NET. It's possible that in your particular

scenario it's not efficient, but it's certainly more scalable than

solutions in which the connection stays open.



How do you implement the two layers of logic? You should be able to

handle one of the layers in stored procedures inside SQL Server/MSDE,

accessed via your data adapter object. If you can be specific, I'll do

my best to help you.



Willis Johnson

.net Enterprise Servers

Microsoft



-----Original Message-----

From: Olav Benum [mailto:wrox@b...]

Sent: Monday, January 21, 2002 12:38 AM

To: ADO.NET

Subject: [ado_dotnet] RE: Resources for local desktop databases





In article <137746@a..._dotnet>, willisj@m... says...

>

> Have you considered MSDE?

I am currently using Access.  I Think MSDE is a kind of

light SQL Server?  I think that would be moving in the

wrong direction for me.



I was thinking more of ways to use Access better, or something

"lighter".  I could perhaps use flat files or XML,so that I have only on

layer of database logic?  Or are there any ADO.NET oriented database

software?



Now with ADO.NET I am essentially taking a copy of most

of the data in my database, processing it, and writing it

back.  This is not very efficient, it is also quite complex because I

have two layers with logic.



(My application should also be easy to deploy)



Thanks!

Olav














$subst('Email.Unsub').