[AccessD] Non-updateable Queries

Based on what I saw, it appears there is nothing inherently wrong with how
I've normalized the data. However, my question seems to be...now that I have
this data so nicely normalized, how can I query it in a meaningful way so as
to be able to update the data? Ideally, the data entry person would like to
see a list of people along with their equipment and location, then be able
to change any portion of the information as reassignments occur.
 Mark


 On 10/27/05, MartyConnelly <martyconnelly at shaw.ca> wrote:
>
> Maybe have a look at this data model for ideas and it's associated
> business rules.
>
> http://www.databaseanswers.org/data_models/inventory_of_servers_in_wyoming/index.htm
>
> There are a couple hundred here too.
> http://www.databaseanswers.org/data_models/index.htm
>
> Admin Sparky wrote:
>
> ><For best viewing, a mono-spaced font is recommended.>
> > Group,
> > Please comment on the table structure noted below. I chose this
> particular
> >scheme because locations are the least likely to change and are forming
> the
> >cornerstone of an Access-AutoCAD application. My problem concerning data
> >updates is that equipment is most easily identifiable with a person, not
> a
> >location. But, a non-updateable recordset occurs when these tables are
> >combined in a query. So...what is an acceptable method of approaching
> this
> >situation?
> > |--tblLocPers---tblPersonnel
> > |
> > |--tblLocPC-----tblPCs
> >tblLocations--|
> > |--tblLocMon----tblMonitors
> > |
> > |--tblLocPrntr--tblPrinters
> > Mark
> >
> >
>
> --
> Marty Connelly
> Victoria, B.C.
> Canada
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>