[AccessD] New database design for MS SQL

...questions? ...not me ...I'm actually sorry Jim asked :)
...until I read that, I thought my schemas were so cool, eh.
William Hindman
----- Original Message ----- 
From: "Charlotte Foust" <cfoust at infostatsystems.com>
To: "Access Developers discussion and problem solving" 
<accessd at databaseadvisors.com>
Sent: Thursday, April 05, 2007 3:06 PM
Subject: Re: [AccessD] New database design for MS SQL


> Eeek! How on earth would I do that??
>
> I can explain that we use a data tier that abstracts the actual data
> structures by building "entity" classes that implement a typeddataset
> for that data entity and interface classes that define what the data
> providers will expose for the entity.  The entity/typeddataset can
> address and manipulate a single table or multiple related tables
> simultaneously.  We use an OleDbProvider project that houses the SQL (in
> XML files) and code classes specific to a related group of tables and
> their children.  The entity classes call into the data provider classes,
> so the code to do a particular thing (i.e., get the next ID number for a
> particular table for a particular set of parameters) is in a single
> location.
>
> We build "business rules" into the entity classes that take care of
> things like returning an exception if a record is being deleted and
> there are related records that need to be deleted or reassigned.  We
> also use them to cascade changes/deletions/insertions to tables where it
> can't be done automatically.  For instance, when we create a new Well
> record, the data tier automatically creates and initial wellBore record
> and doesn't allow the user to delete that wellbore except by deleting
> the well.  Someday, if I ever find the time, I'm going to try modelling
> this in Access!
>
> Any questions?? LOL
>
> Charlotte Foust
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
> Sent: Thursday, April 05, 2007 11:24 AM
> To: 'Access Developers discussion and problem solving'
> Subject: Re: [AccessD] New database design for MS SQL
>
> Hi Charlotte:
>
> So let us see some samples... Most of us here are at least conversant in
> .Net and would find it very informative.
>
> TIA
>
> Jim
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
> Foust
> Sent: Thursday, April 05, 2007 11:12 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] New database design for MS SQL
>
> Interesting article, particularly since it seems to encompass a lot of
> the design approaches we already use in VB.Net.
>
> Charlotte Foust
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
> Sent: Thursday, April 05, 2007 10:18 AM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] New database design for MS SQL
>
> Hi All:
>
> There seems to be an interesting design for MS SQL Database. For those
> who have used classes here is a new implementation:
>
> http://msdn2.microsoft.com/en-us/library/bb245675.aspx
> http://www.sqlserverbible.com/ordbms.htm
>
> Jim
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>