[AccessD] Data interface The best way

Yeh, your too old too....:-) You are really at your prime of life; like me
nearing official retirement age and freedom though my revised retirement
time has been extended until my early eighties...

>> I went cold turkey a week ago when my backlit display lost its backlight.
A full week!!! My sympathies.

It would be great if you could cobble something together and do not worry
about sending a late email, I will be up. :-)

...and again thanks.
Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Thursday, October 13, 2005 11:08 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Data interface The best way

You're too old??  I'm 61!  I don't have anything offhand but I can dummy
something up this evening, I think.  My PC is supposed to be back in my
hands tonight (I went cold turkey a week ago when my backlit display
lost its backlight), so I'll see what I can do.

Charlotte


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Thursday, October 13, 2005 11:02 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Data interface The best way


Thank you very much for that Charlotte. 

Do you have a small example of the implementation...does not have to
work... but something that gives substance to the concept? (I need to
make a decision quickly as I am running late and it looks like (a) long
night(s)
ahead.)

TIA
Jim 

PS I am too old for this....

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Thursday, October 13, 2005 10:27 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Data interface The best way

We use typed datasets and build a data "entity" in the solution that
inherits that typed dataset and handles validations, update calls,
fills, etc.  We build dataproviders for each typed
dataset/entity/interface and let it handle creating the connections and
command strings, building the data adapter and passing a filled "entity"
back to the calling routine.  We actually store the SQL for these
commands in xml and look up the one we need, passing the parameters in
through the dataprovider.  It works quite well. 

Our code doesn't distinguish between back ends because right now, we're
simply using the OleDb provider for everything.  The SQL provider might
be faster, but we would have to write separate code to implement it and
our app needs to be able to work against either backend so we're
husbanding our resources<g>.

Charlotte Foust