If I want to make a new database with a selected number of records of my original database, it seems that the only way of doing it is by making a backup of the original database then change all the names of all the forms and reports, then marge the backup with the original, then copy the records, then trim one of the databases.
¿Is there a simpler and shorter way of donig this? ???

I am going to try to explain in detail what I want to do.
1. I have a mother database where I introduce information every day.
2. I also have many similar databases (one for each client) and every day I have to distribute the information from the mother database to each of the clients databases. Some records go to a client and some others to another. All databases are similar.
3. I do not want to erase any records from the mother database because I use that database for searching globally.
4. In other words all I need to do is copy selected records from a database to another similar one.
5. This was very easily done in Q&A but with Sesame I face the problem that I cannot merge two similar  databases and therefore cannot copy the records without having to change the names of ALL forms and reports!
6. There must be an easer way

It seems that we are still no talking about the same thing.
I am going to go in more detail.
I am rendering now a new service that I did not offer with Q&A.
My new database is relational but with only two tables.
However, the first table is similar to the old flat Q&A database.
So now my mother database is relational and similar to all the receiving databases.
And I do have a new Client field in the new database.
So every day after feeding the new information to the mother database I perform one search for each client and get a group of records for each client that I need to copy into each client receiving databases.
To do that it seems that I have to merge each of the client databases with the mother in order to perform the copying operations.

I definitely need to have separate client databases because the clients demand it.
Export/import is not a bad idea.
I looked into Sesame´s export facilities and liked what I saw.
The idea is a little "special" since export/import was designed to pass information from non-sesame databases. But I see no reason not to use it between Sesame databases.
This looks specially easy because the information that I have to copy does not include the information on the subform.
I will go into comma separated export/import.
Maybe I can write a Macro for each client.
However, I still think this means a lot of trouble for an operation that should be straightforward.
I suggest Sesame comes up with a utility that let users copy records between Sesame databases without having to merge them.