How to Duplicate Table With Records in FM

[Caio Euzébio]

Hi Guys,

I new in FM, and i trying to create a application that i need 2 tables with same records to make a look up search.

However i not getting duplicate my table, once i duplicate it my table is Pasted only with fields but without records.

How can i duplicate mu table with records?

 

I Tried export and import also, without success.

 

There are any script, or method to duplicate table records?

 

Thank you guys.

[Ocean West]

When you import records you can choose to create a NEW table it will create a table with all the fields

[Caio Euzébio]

Yes Ocean,

But the most important to me is table records, not fields.

And FM is not copying getting the records, only fields.

[Ocean West]

When you perform import close the item "NEW TABLE" it will create a new table and import the records

 

[Caio Euzébio]

Thank you Ocean.

It worked, new i able to duplicate my tables to work.

 

Thank you so much.

 

Have a good afternoon.

[comment]

1 hour ago, Caio Euzébio said:

i need 2 tables with same records to make a look up search

I am not sure what "a look up search" means. I don't think you need two tables with same records for anything. 

 

 

Edited June 26, 2019 by comment

[LaRetta]

Hi Caio, 

I agree with Comment.  It is _very_ unusual to duplicate a table's records.  Instead, why don't you simply duplicate the table occurrence?  Select the table occurrence of the table you want from within the graph then click lower left the ++.  

With this duplicate table occurrence, you can place it elsewhere, such as connected to another table, and use the same records  - no need to duplicate records at all!  If you duplicate the records, such as using import into a new table, you run the risk that the records will never be up to date.

If you explain why you feel you must duplicate the table, or explain what 'a look up search' means, as requested by Comment, then we could help you with a better method.  Just an idea!  And welcome to FMforums! 😀

Edited June 26, 2019 by LaRetta
Corrected 'right' to 'left' hahah!

[Caio Euzébio]

Hi LeRetta,

I need that User request 10 different itens in the same screen.

And all these fields need to have you own table and relations for not get informations of previously or next one.

And all these fields will need to be take for a script and populate a database table of requests history.

If i have only one table with informations about product, is i create 10 different Edit Box in the same screen, all box will get the same informations, for this reason i need 10 different tables.

 

[comment]

It is difficult to understand your explanation without knowing what these things represent in real life. Offhand, it seems you need a structure similar to an invoicing solution. This would have 3 tables: Requests, Products and a join table of RequestProducts (for lack of a better name) connecting the two:

A user making a request would start by creating a new record in Requests, then use a portal to the RequestProducts table to create a record for each product included in the request. This allows a request to include any number of products - and no data needs to be duplicated.

 

[Caio Euzébio]

Like This.

I need to make this Layout functional with DB relations. one line of this lay out need to populate one line of table requests.

[comment]

Yes, that's exactly what a portal would accomplish.

Note that once you have selected the products to include in the request, you can print/view the request using a layout of the join table in list view, with the request's data placed in summary parts.

[Caio Euzébio]

I will share my progress.

[DanH]

On ‎6‎/‎26‎/‎2019 at 1:31 PM, LaRetta said:

Hi Caio, 

I agree with Comment.  It is _very_ unusual to duplicate a table's records.  Instead, why don't you simply duplicate the table occurrence?  Select the table occurrence of the table you want from within the graph then click lower left the ++.  

With this duplicate table occurrence, you can place it elsewhere, such as connected to another table, and use the same records  - no need to duplicate records at all!  If you duplicate the records, such as using import into a new table, you run the risk that the records will never be up to date.

If you explain why you feel you must duplicate the table, or explain what 'a look up search' means, as requested by Comment, then we could help you with a better method.  Just an idea!  And welcome to FMforums! 😀

I found this comment valuable to me. I needed another association table to look up a persons e-mail address directly instead of hard coding it. this worked flawlessly.  Thanks.