Link fields if found

[kmerid59]

I have a registration from that has numerous fields and would to like if the
register this year pull all the fields from old over to new db - I can either
use exsisting excel or import old into acess. The member nbr is the primary
key

I am using access 2007

 

[John W. Vinson]

I have a registration from that has numerous fields and would to like if the
register this year pull all the fields from old over to new db - I can either
use exsisting excel or import old into acess. The member nbr is the primary
key

I am using access 2007

A Form is just a window, a tool to view data in the table. You can't pull data
from a form because it doesn't exist there - it exists in a table.

What is the table? What's its structure (fieldnames and datatypes)? Why do you
think you need a new database? If you have the same data from year to year,
normally you would have two tables, one for the static data and another for
the year to year changing data, in a one to many relationship?

 

[kmerid59]

It is actually a table with field names. I want a new database because not
the same people register year to year and and we have to create credentials
and badges for those that do register, so i would like it that if you are in
my pastreg table and then i have 2010reg table that if i type in your member
nbr and you were in pastreg it would pull over all fields so that we do not
have to retype everything just verify add, phone, emal etc

 

[PieterLinden via AccessMonster.com]

It is actually a table with field names. I want a new database because not
the same people register year to year and and we have to create credentials
and badges for those that do register, so i would like it that if you are in
my pastreg table and then i have 2010reg table that if i type in your member
nbr and you were in pastreg it would pull over all fields so that we do not
have to retype everything just verify add, phone, emal etc
[quoted text clipped - 10 lines]

normally you would have two tables, one for the static data and another for
the year to year changing data, in a one to many relationship?

Bad idea. Just add a year to the registration table and filter off that.

 

[kmerid59]

Ok that would work - was trying to make it too difficult but that will work -
thanks

It is actually a table with field names. I want a new database because not
the same people register year to year and and we have to create credentials

[quoted text clipped - 8 lines]
Bad idea. Just add a year to the registration table and filter off that.