filemaker pro 16 copy all fields from one table to another

Microsoft has an article with examples about those methods.

The attachment data type (as well as MVFs) forces you to use “row-by-agonizing-row” programming when dealing with a MVF field, it’s a twofer with Attachments field because you would have to use the LoadFromFile or SaveToFile methods. This has created a problem for managing resources in our standard library because we want to use the MSysResources but we can’t easily update or insert them in bulk. We love using the image gallery and themes, both of which depend on a system table, MSysResources which unfortunately uses the attachment data types. Indeed, any tables that contains such data type force you to do a lot of code and for that reason alone, we avoid using such data types normally. For one, you’d be unable to use queries to insert or update several records in one go. This all boils down to the fact that an Attachments data type is actually a Multi-Valued Field (MVF), and these come with several problems. However, a quick google search will usually show that they are best avoided. Since Access 2010, Access has supported Attachments data type which on the surface seems like a convenient feature for storing small images or files. Truck Owner Operator Software and Web Solution.

The Perfect Trifecta Solution for Efficient Medical Record Keeping.Safety Training, Incident and Accident Tracking Tool.Monitoring Production Scrap Levels with Power BI.Managing a Multi-Billion Dollar University Endowment Fund.Labor Union Dues and Membership Management System.Insurance Claim System to Reduce Processing Time.Elected Officials Database with Ethics Form tracking.Custom Quoting and Proposal Sales Force Solution.Amazon API Integration with Microsoft Access.Convert ADP file to ACCDB (regular Access file).

Enable Microsoft Access to work from home.Microsoft Access Database Inconsistent State Error.

Filemaker pro 16 copy all fields from one table to another