Recent content by kawaisunn

jdraw: I don't understand why 1-1 may be a bad idea in the relationship of these two tables, but I am open to suggestion and willing to do research. Yeah, newb and all that. My argument for 1-1 is that in no case should there ever be a property in the child that is not in the parent, or in the...

Gemma-the-Huskey: I do see what you mean. I set the relationship between tables lowbrow by clicking on the link and tagging check boxes. It may very well be that my related keys are linked backwards ie. from the child to the parent. That would certainly explain it if the relationship between the...

Hopefully some of the information I provided above will help explain. Actually, for the task at hand, I would LOVE it if deleting any key from the main table would remove that reference from that database forever (except in my TrackChange table, of course).

The child table drives our web interface. In this case, it is a free public portal to abandoned mine property locatations, as well as other data such as production, water quality etc. We are a non-profit entity funded partially by the state, partially by grants, and attached to a land grant...

I'm a newb to Access and SQL and database management. I have a main table and a dependent table with a 1 to 1 relationship, relationship integrity and cascade update and delete. I used an append query after I had modified several records, and after the append deleted one of the records from the...

Jumped into Access and DB management with both feet, without checking the water. I inherited a database that began as handwritten unpublished accounts from the 1800's, to state published data, eventually to dBase, then migrated to Access. I work for a state agency and nearly all of our data...