Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

copy contents of one file to another

Featured Replies

  • Newbies

I have two similar contact files. One big, one small. I want to put the records from the small one into the big one, one at a time if I need to. How do I create a new record in the big file, and copy fields from the small file to paste into the big one. I can use a relationship but not lookups because the small file will eventually go away. I've tried a simple script starting in the small file using an external subscript which creates a new record in the big file and then selects a field in the small file, copies that and then pastes it in the selected field (based on the relationship I set up which I'm now realizing doesn't work)

Any reason why you can't just import the records?

If not, give it a try. Make a backup of your file first, then try the "Import Records" menu option. It will walk you through the process.

  • Author
  • Newbies

I'm actually trying to set up a script so a user can click a button to copy a specific record and create that new record in the big file.

That is what I were doing to export some contacts of my Main Contact file to my Palm Contact File.

1 constant relationship from Palm Contact to Main Contact using global = 1 at left and index calc = 1 at right. (g_Hook in Palm, cHook in Main)

a set of global fields for adress, phone, name, ID.

The script goes in Main Contact file :

Set globals

External script - New records

External script - Set fields

(Setfield (Name,Constant::g_Name),....

I now use a portal and it is easier.

I can use a relationship but not lookups because the small file will eventually go away

Well, this would not be a problem as a lookup field is not a related field...

Further to what Ugo was saying, a lookup field might be a good way to go since the lookup field data is stored. Do not confuse it with a related field. The data will only change when you enter a new, valid key in the key field. When you're ready to get rid of the source database, you can simply convert the fields into regular fields if you like. The data will remain.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.