Best way to do this.

#21

We don't quite know enough here i don't think. But on the surface I
would say open a tc on the foreign key link to the table that has the
data you might want. Setrange on it. If there is 1 or more records find
the last one (scan if more than one) then grab the data from the fields
and pump it into your new record.

Seems to me that if the data would be that common between the 2 records
though they really should be in separate tables and you should just link
to that data for each of the records with data that changes.
HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

Craig wrote:

Quote:

The setup:
I have developed an anesthesia assessment form attached to our clinical
database. This form's data model has two tables in it. There are times when
these patients are repeat patients. I would like to be able to give the user
easy access to the previous assessments and even copy some of the data from
a previous encounter that the user will choose.
I don't want the current record to show up on the form showing the previous
records

The question:
Is it better to use setgenfilter and just filter for the patients medical
record number OR have the form run a query and copy all the previous
records to a new set of tables and have them view the records in a new form
and do what they need to do?

I think the first one is the most elegant but I don't see a way to do
setgenfilter and NOT have the current record also viewed.

Thanks,

Craig Futterman

#22

We don't quite know enough here i don't think. But on the surface I
would say open a tc on the foreign key link to the table that has the
data you might want. Setrange on it. If there is 1 or more records find
the last one (scan if more than one) then grab the data from the fields
and pump it into your new record.

Seems to me that if the data would be that common between the 2 records
though they really should be in separate tables and you should just link
to that data for each of the records with data that changes.
HTH

Denn Santoro
President
Resource Development Associates
http://www.RDAWorldWide.Com
Offices in the United States and Germany
Providing solutions to health care, business, governments and
non-profits since 1982

Craig wrote:

Quote:

The setup:
I have developed an anesthesia assessment form attached to our clinical
database. This form's data model has two tables in it. There are times when
these patients are repeat patients. I would like to be able to give the user
easy access to the previous assessments and even copy some of the data from
a previous encounter that the user will choose.
I don't want the current record to show up on the form showing the previous
records

The question:
Is it better to use setgenfilter and just filter for the patients medical
record number OR have the form run a query and copy all the previous
records to a new set of tables and have them view the records in a new form
and do what they need to do?

I think the first one is the most elegant but I don't see a way to do
setgenfilter and NOT have the current record also viewed.

Thanks,

Craig Futterman

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Best way to do this.

comp.databases.paradox comp.databases.paradox

Re: Best way to do this. - 05-13-2008 , 07:45 AM

Re: Best way to do this. - 05-13-2008 , 07:45 AM