Script to duplicate record to new database

[Beccapori]

Hi,

I am very new to using FileMaker Pro 7 (or any version) so please forgive me if I'm asking a basic task. I have been working to get a button (made and ready) to have a script that will duplicate and then move the record and place it in a new database. Essentially, I have many records (750+) that need to be organized according to whether or not they are a chemical. I need 1 database that has a list of all the chemicals with no other types of supplies. Right now, there is no indication as to what the record is. I'm hoping that the button will identify them as a chemical and then place them into a new chemical database.

What kind of scripts should I use? It looks like there are many pre-made scripts that need to be modified in order to run my specific task, but I do not know which ones to use or what order to use them in.

Any suggestions would be very helpful. If I wasn't clear in what I am trying to do, please ask me to explain further.

Thanks,

Beccapori

[Søren Dyhr]

Hi and welcome Beccapori. Filemaker have for the last decade been an implementation of theory for relational databases, which is a quest to solve redundancies ...so what you ask for is in it's strictest sence a violation of these thoughts.

Wouldn't it be better if there were provisions of tools to recall found sets of the data instead of having a new database each type??? Since they belong to the same base originally is there some sort of unifomity in the contents. What it takes is to make an extra field in the base that tells which type (the product group) the item belongs to, and make the script make the search in that field to produce to found set.

Now this is what you're allowed to do with whatever databasetool flat or relational, you wish for. Where it gets relational is that you make a record for each product group in another table, and store the recordID's for each member in the group in a keyfield as a multilinekey. This keyfield is then via the relational tools connected or linked to a foreighn key, which in this case is the individual records ID. This means that you can show a list of all records in a portal showing the intended found set.

--sd