Hi guys,

I am a newbie to Filemaker and need your help.

Ok so here is my problem:

I have one contact database and now i want to have a second

seperate contact database. what I want is that the second database gets specific contacts from the first database.

For example: I want in the second database only the contacts that are in my hometown.

The reason I want to do this I need another contact database with the contact but want to include another informations regarding them, that I don't want to have in the first one.

I hope I could explain my self good.

I am sorry for my bad english.

Thank you very much in advance.

Cheers,

Martin.

It seems as though you dont really have to have 2 seperate databases. There are many different ways that you can hide fields or data including using different layouts and permissions.

If you definately want 2 databases, the easiest thing to do it just copy the database to another file and delete the records from the second file that you do not want. This way you do not have to do the whole export / import thing.

hmm... but this way I have to add that contact seperately in two databases. i want it to work that way:

Add contact into database 1

open database 2. database checks for new records specific to my criteria as said for example only people from my hometown.

i am surely open for other workarounds.

thanks for your help.

cheers,

martin.

You can import for File 1 into File 2 ( update existing records )

how can I import that with matching my criteria.

Say import contacts from Database 1 but only that ones that have in there Country1 field Boston stated ?

thanks for ther help.

cheers,

martin.

You perform the find first. When you have your found set, then import. Makre sure you leave your File 1 open with the found set.

Edited February 17, 200916 yr by Guest

I would suggest you keep all your contacts in a single table. If there is a type of contact that requires additional fields, you can either leave those fields empty for the other types (simple, and easy to implement in version 10, where you can load a different layout for each type), or put the additional fields in a related table with a one-to-one relationship to the Contacts table (a bit more efficient, but not so simple to implement).