A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Link fields if found



 
 
Thread Tools Display Modes
  #1  
Old April 21st, 2010, 03:55 PM posted to microsoft.public.access.tablesdbdesign
kmerid59
external usenet poster
 
Posts: 1
Default Link fields if found

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
  #2  
Old April 21st, 2010, 04:29 PM posted to microsoft.public.access.tablesdbdesign
John W. Vinson
external usenet poster
 
Posts: 18,261
Default Link fields if found

On Wed, 21 Apr 2010 07:55:01 -0700, kmerid59
wrote:

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?

--

John W. Vinson [MVP]
  #3  
Old April 21st, 2010, 07:03 PM posted to microsoft.public.access.tablesdbdesign
kmerid59[_2_]
external usenet poster
 
Posts: 2
Default Link fields if found

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

John W. Vinson wrote:
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?


  #4  
Old April 22nd, 2010, 12:29 AM posted to microsoft.public.access.tablesdbdesign
PieterLinden via AccessMonster.com
external usenet poster
 
Posts: 307
Default Link fields if found

kmerid59 wrote:
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

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

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

--
Message posted via http://www.accessmonster.com

  #5  
Old April 22nd, 2010, 12:41 AM posted to microsoft.public.access.tablesdbdesign
kmerid59[_2_]
external usenet poster
 
Posts: 2
Default Link fields if found

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


PieterLinden wrote:
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]
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.


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 12:47 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.