Jump 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.

table to table import problem

Featured Replies

I’ve got records in table “A” (488 fields) that I want to import into Table “A Archive” (488 fields) in the same file. Both tables have identical fieldnames in the same order. Actually, I created “A Archive” by duplicating (copy/paste) table “A” in manage database and renaming it. I just want to be able to dump the records from “A” into “A Archive”. Is there some magic that I need to do on the relationship graph or is there a trick to importing from “A” into “A Archive”? I haven’t been able to make it work. Also, I’m getting “” showing up in “A Archives” layout. Thanks for your help.

Did you try File > Import records > File...

I’ve got records in table “A” (488 fields) that I want to import into Table “A Archive” (488 fields) in the same file.

Ehm?? Who would need that, hardly normalised is it?? Please note this isn't a spreadsheet debates forum!

--sd

  • 3 weeks later...

interesting... I'm trying to do the same. There should be a way of doing this without using set field, which seems overkill for a table with 488 fields.

In my case, I need to archive the old records that will no longer be used. By transfering those to the second table, users will still be able to view the old data in a second layout, while clearing the main table from the records no longer needed there.

I wonder what the missing bit here is, import between tables inside a solution is just adding the file itself in the reference list??

--sd

A database model you might want to consider is what is referred to as Type/SuperType.

Basically, you'd have a base table that has all the data. Then, you have two "satellite" tables that hold the IDs of a certain type. This will allow you to create a form/list view of just that type.

In your solution, I'd have three tables, ActiveItems, ArchivedItems, Items. It's terrific, because you do not move data between tables, you simply set IDs.

See Fenton's detailed description: Graham Method

Ah that's right Barbara I'm not really getting anywhere mentally today ... it's the old story about management demanding starting all over on a new year with a new table...

--sd

Create an account or sign in to comment

Important Information

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

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.