Microsoft Access

[emir0514]

Hi All,

I have used Microsoft Access in college, a little bit of SQL, but I am no expert.

Here is what I am trying to do:

1. Design a form which promts the user to input their First Name, Last Name, Country, Dollar Amount, Approval Date, and Expiration Date.
For example: John Smith USA $100 6/1/2013 7/1/2014

2. One year later John Smith comes back to renew his membership, is there a way to update the expiration date without having to go through the table and search for his name and overwrite the old Expiration Date & Dollar Amount.
For example: Using the same form and input the new information: John Smith USA $150 7/1/2014 8/1/2015

This way the person inputting the information would never have to mess with the data, it can all be done from the form.
Also is it possible at all to store the historical Expiration Date & Dollar Amount. I want to store the last 5 years worth of data.

Any ideas would be apprciated. Since I am a noob at this it would be even more amazing if someone created an example of this with the fields I listed above and attach it

Thank you!!! & God Bless

 

[dhookom]

emir0514,
In the future, you might want to be a little more explicit with your subject line. "Microsoft Access" is assumed in these fora.

I wouldn't update existing records. I see a new registration or renewal as a transaction.

Duane
Hook'D on Access
MS Access MVP

 

[emir0514]

So even if it is a new transaction, is there a way to tie them somehow? or not show the older one?

What I am worried is suppose you crete a membership on June 1/2013 and it expires June 1/2014
There are times when a renewal would occur before the expiration date.
For example I would be creating a new one that begins on March 1/2014 and expires March 1/2015

So I am worried of the overlap, when I run the report suppose on March 1/2014, it will show TWO expiration dates, one for June 1/2014 & March 1/2015. I want it to only show the most recent one. Is there a way to possibly do this?

Also sorry about my title I will try to be more specific next time. Thanks!

 

[dhookom]

I would have a membership table that has no fields relating to the dues transactions. A user would open a form to either find an existing member or add a new member. The main form would have a subform of transactions related to the member.

Duane
Hook'D on Access
MS Access MVP