H
Harper
FYI.
Say you have a form where the user of that form can delete a record,
say, a student record. You want to have a history of that old record,
though, just in case. So often true in education. There are two schools
of thought. One, that you shouldn't copy records to a table and delete
from the original table. You should just have a field in the original
table with a yes/no deactivate field or attribute.
Some say that it is just fine to want to separate out "deleted" records
with tables rather than queries, because it mirrors a real-world
physical action.
"In fact, I only establish Relationships in Access' Relationships
Collection when I want to enforce Referential Integrity. Often, I may
not want to automatically delete, for example, because it's important
to save the record in a history file, and you have to do that yourself.
Michael Kaplan, whose technical opinions I highly respect, tells me
that establishing the relationship will, in fact, improve performance,
but I haven't suffered too much from slow performance and they are a
Rouyal Pain in the Tender Places when I want to delete a table, or make
some design modifications while developing. But, if yours is a Decision
Support System, rather than a strategic business system, you may not
need a history file."
http://groups.google.com/group/comp...3e7d21a13212a/66ec0535a8470c3#66ec0535a8470c3
Say you have a form where the user of that form can delete a record,
say, a student record. You want to have a history of that old record,
though, just in case. So often true in education. There are two schools
of thought. One, that you shouldn't copy records to a table and delete
from the original table. You should just have a field in the original
table with a yes/no deactivate field or attribute.
Some say that it is just fine to want to separate out "deleted" records
with tables rather than queries, because it mirrors a real-world
physical action.
"In fact, I only establish Relationships in Access' Relationships
Collection when I want to enforce Referential Integrity. Often, I may
not want to automatically delete, for example, because it's important
to save the record in a history file, and you have to do that yourself.
Michael Kaplan, whose technical opinions I highly respect, tells me
that establishing the relationship will, in fact, improve performance,
but I haven't suffered too much from slow performance and they are a
Rouyal Pain in the Tender Places when I want to delete a table, or make
some design modifications while developing. But, if yours is a Decision
Support System, rather than a strategic business system, you may not
need a history file."
http://groups.google.com/group/comp...3e7d21a13212a/66ec0535a8470c3#66ec0535a8470c3