Duplicate record from one table to another

[Kate1234]

What is the most efficient way to duplicate a record from one table to  
another?

Katherine

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/

[Steve Cassidy]

Katherine,

Simply import the record.

Steve


On 21 Jul 2008, at 12:04, Katherine Wendt wrote:

> What is the most efficient way to duplicate a record from one table  
> to another?


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/

[FM Talk]

I agree that importing is one of the best ways to go, but I have to  
add something to that.
If there are a lot of records in your export table and you need only  
some of them duplicated in the import table, first make a found set  
of records in the export table and run the import in the import  
table. This way only the found records will be imported, not all the  
records of the export table.
I hope this will help.

On Jul 21, 2008, at 7:04 AM, Katherine Wendt wrote:

> What is the most efficient way to duplicate a record from one table  
> to another?
>
> Katherine
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
> Manage your subscription: http://www.ListSearch.com/FileMaker/
>

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/

[Kate1234]

Ideally (but not critically) the method will be executable from the  
web, and importing records.

Is there an elegant method that would also work through a browser? I  
am REALLY unfamiliar with making a solution accessible on the web -  
this is my first attempt.


On Jul 21, 2008, at 8:16 AM, Steve Cassidy wrote:

> Katherine,
>
> Simply import the record.
>
> Steve
>
>
> On 21 Jul 2008, at 12:04, Katherine Wendt wrote:
>
>> What is the most efficient way to duplicate a record from one table  
>> to another?
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
> Manage your subscription: http://www.ListSearch.com/FileMaker/

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/

[Søren Dyhr]

Den 22/07/2008 kl. 15.48 skrev Katherine Wendt:

> Ideally (but not critically) the method will be executable from the  
> web, and importing records.
>
> Is there an elegant method that would also work through a browser? I  
> am REALLY unfamiliar with making a solution accessible on the web -  
> this is my first attempt.

Hopefully are you aware what you're up against here?? Everything  
duplicating and synchronizing is perverting the gist of any relational  
tool, you need to rethink if this is really what you wish to and first  
and foremost give any future replier to this thread or any thread you  
initiate for that matter: Context and purpose ... please??

--sd


--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/

[Kate1234]

This is a membership database. One file, FMP9, multiple related  
tables. The software gets used by non-computer people who are having  
trouble dealing with terminated members still being in there and  
therefore needing to trap to eliminate them from finds and such. The  
only place the old records get in the way is in the table listing the  
families. Other tables, such as payments, usage, names of kids, can  
keep old data in them without bothering anybody.

It would be nice to have a clean slate of families each year, along  
with a single repository for the terminated families for those  
instances when they resurface. Not terribly often, but people do move  
back to town, or wonder whether they got their refund two years ago.

This is the reason the usual way of archiving, just make a duplicate  
of the whole file before deleting the offending records, doesn't work  
well. I want all of the old families to be gathered together into a  
single resource, regardless when they Terminated.

The plan was to have two tables within the file, one FamiliesCurrent  
and one FamiliesArchived, and a family would be in one or the other  
but not both.

The relationship graph shows FamiliesCurrent at the center of all of  
its relationships. The FamiliesArchived file is at the center of  
another set of relationships to those same files.

Families would only be moved one at a time from one table to the  
other, not in batches.


On Jul 22, 2008, at 1:06 PM, Søren Dyhr wrote:

>
> Den 22/07/2008 kl. 15.48 skrev Katherine Wendt:
>
>> Ideally (but not critically) the method will be executable from the  
>> web, and importing records.
>>
>> Is there an elegant method that would also work through a browser?  
>> I am REALLY unfamiliar with making a solution accessible on the web  
>> - this is my first attempt.
>
> Hopefully are you aware what you're up against here?? Everything  
> duplicating and synchronizing is perverting the gist of any  
> relational tool, you need to rethink if this is really what you wish  
> to and first and foremost give any future replier to this thread or  
> any thread you initiate for that matter: Context and purpose ...  
> please??
>
> --sd
>
>
> --
> This list is a free service of LassoSoft: http://www.LassoSoft.com/
> Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
> Manage your subscription: http://www.ListSearch.com/FileMaker/

--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/

[Søren Dyhr]

Den 22/07/2008 kl. 21.11 skrev Katherine Wendt:

> Families would only be moved one at a time from one table to the  
> other, not in batches.

Never the less is it just as relationally unhealthy as this:

http://www.nabble.com/Aggregating-numbers-from-different-tables-to18298654.html

The only real difference should be a single boolean attribute active/
passive, otherwise is it a complete entity duplication if you insist  
on having two tables, you would better be off studying de-duping  
strategies, look say here:

http://www.fmforums.com/forum/attachment.php?attid/13677/

Where I show how to use the Replace in Globale as Agnès have named it,  
in the script-listing in the very end:

http://sixfriedrice.com/wp/deleting-duplicate-records-in-filemaker/


--sd
--
This list is a free service of LassoSoft: http://www.LassoSoft.com/
Search the list archives: http://www.ListSearch.com/FileMaker/Browse/
Manage your subscription: http://www.ListSearch.com/FileMaker/