Transferring data from one database to another.

[nadia]

Hi,

I am a new to script writing in Filemaker and really need some help. I am creating 3 databases that are all related to each other and have a number of common fields. I would like to set it up so that I can enter data into database A and then update database B for the fields the have in common. But I want the data from only that record (say record 1) to be sent to database B.

In other words I want to send data from fields x y and z in record 1 of Database A to fields x y and z in a new record in Database B. If a record matching the contents of field x already exists in Database B I want it to update that record and not make a new one.

I hope I have made this clear enough!!

I tried the import function but that obviously imports from ALL the records in Database A to Database B and I am not sure if I can get it to just do that from one particular record.

Thanks for your help,

NE

[SassyTexan]

Create a relationship between the 2 files. Check the box in the relationship that allows creation of new record. Then use a portal to enter the information into the File B. Unless you MUST have it stored into 2 locations. If so why?

What I do is create a main data entry site based on fields from other files using the method above.

[stanley]

Nadia:

Why are you storing the same information in different locations? What happens if the information is changed in one location, but not in another? You're much better off storing information that belongs in database A in database A, and what belongs in database B goes in database B. You can always see the data through your relationships, and if you change related data in one place, it changes wherever it is shown.

-Stanley

[nadia]

Thank you so much for your advice.

Actually the need to keep the same data in multiple places is dictated by our needs in terms of analyzing and using the data as well as the different people looking at it. This is for a scientific study in which we are recording a number of different parameters.

We are breeding some animals so in database A we keep track of the who is in the cage, how many males, how many females their dates of birth, ID #s etc. We also record the birth of all new litters on this page and some details such as DOB etc. but the individual information on each animal in the litter has to be kept in database B where we will record the sex of each new animal born, their coat color etc. Since over the years there are so many new litters in one cage that keeping all that information in the cage database (A) gets to be too cumbersome.

But everytime we record a new litter in the litter database (A) we also want it to automatically create a record in B and put in the ID #s of the mom and dad and other static information like that so we do not have to re-enter it. When we evaluate our data we have to look at the number of litters that were produced in each cage as well the the number of newborns in each litter. For another project we need to keep track of the individual charecteristics of each new animal but we do need to have the parent's info there so we can sort or search by that data.

So having explained our reasons, I will try the portal idea (I don't think my boss will like it too much though) but if you have any further suggestions I will be very happy to test them out.

Thanks again for your help,

Nadia

[stanley]

Nadia:

So, essentially, you've got a "Cage" database, and an "Animals" database, right? If that's so, then the data should be divided pretty clearly - things that have to do with the cages themselves (probably very little, I would imagine) would go in "Cage", and things that have to do with the animals themselves (most of what you've mentioned) would go in "Animals."

For example, the data for one animal would include which cage it was born in, and to which mother, etc; then, in the "Cage" database, you can have a relationship back to the "Animals" database, which will show who was born there and when, etc... Within the "Animals" database you can have relationships so you could easily see who was born by, and to, whom, just from looking at the one record. Perhaps you know all this stuff already, but I thought I would mention it anyway, because portals can really simplify the user's experience as far as viewing complex sets of data.

Your boss may not like the idea, but seeing it in practice converts even the blind.

-Stanley

[nadia]

Hi Stanley,

Thanks again. I understand what you are saying but we still need the data to be present in both the cage database as well as the animals just because of the way are record keeping requirments are set up. Your solution to use portals is really good and would make things simpler but we do need to search based on many different fields in each data set.

Any ideas?

Nadia