Connecting Tech Pros Worldwide Forums | Help | Site Map

joining databases

Familiar Sight
 
Join Date: Jul 2006
Posts: 181
#1: Jun 14 '09
Hi, I wonder if there is a solution to this. I have asked this before but still not sure of what to do.
I have two access databases, one old and one new. I need to transfer all the records from the old one to the new one. The trouble is the old one does not have a three field that the new one has. They are Password, PasswordEncrypted, PasswordKey. These are required fields and of course generated by some code in the admin section so i need to enter something in each.

Is there a way to move all the records and at the same time create entries for these three fields. I have over a thousand records and dont want to have to enter them one by one in the user admin section.
Thanks for any advice.
Richard

NeoPa's Avatar
Administrator
 
Join Date: Oct 2006
Location: London - UK
Posts: 15,747
#2: Jun 15 '09

re: joining databases


That really depends on what needs to be done in the Admin section to create the three extra values required.

It's hard to answer a question when half of it's missing.
Familiar Sight
 
Join Date: Jul 2006
Posts: 181
#3: Jun 18 '09

re: joining databases


Hi, Actually I worked it out by changing the database fields to Required = No, so I was able to populate users without all fields requiring data. It turns out that the PasswordEncrypted and PasswordKey fields we only used when members were not allowed to store cookies. If you allowed them its not used so I was able simply to repeat the same code for all users.
Thanks anyway for your help
Richard
NeoPa's Avatar
Administrator
 
Join Date: Oct 2006
Location: London - UK
Posts: 15,747
#4: Jun 19 '09

re: joining databases


Thanks for the update Richard.

Ironically enough, that also provides the perspective missing from the original post. Sounds like you've got it all sorted though anyway.

There are two basic ways to get past this problem generally :
  1. The way you used (fundamentally). Change the design of the table such that the fields that are currently unavailable are not required. This can be changed back later if required, after the data is in place.
  2. Create the data in a separate table first, moving it across only when it is complete and complies with all stipulated rules.
Reply