Jump to content

This topic is 7814 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Not really, but there are some workarounds. If a field in dbA is a complex calculation, you can select & copy the whole calc to clipboard. Then in dbB, make a new calc field and paste in the calc (assuming all calc references are to fields with the same name). This is very useful for making a complicated calc field in one db, then duplicating it in a bunch more.

If dbA has, say 30 out of forty fields you want to "import" into dbB, you could make an empty clone of dbA, delete the ten unwanted fields, then create the fields in dbB that aren't in dbA. Then import all data from the original dbB into this new db, rename it & delete (or archive) the original.

If there are too many fields not common to both db's, then you're probably out of luck. It'll be a bunch of work one way or the other. You *can* import scripts (assuming field references are in order), and copy entire layouts from one db and paste into another (again, as long as field names are the same).

Steve Brown

This topic is 7814 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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