Add a new transaction to an existing record in access

[Guest]

How do I add a new transaction to an already existing record (member). I need
to basically create a new transaction for a record that already exist. When
I pull up a record it shows the last data entered. I would like to make a new
record for the same account without appending on to what is already there.
Thank You in advance.

 

[John Vinson]

How do I add a new transaction to an already existing record (member). I need
to basically create a new transaction for a record that already exist. When
I pull up a record it shows the last data entered. I would like to make a new
record for the same account without appending on to what is already there.
Thank You in advance.

"Transaction" is a term of art in Access... but not in the way you're
using it.

What is the structure of your Tables? Do you have a Members table
related one-to-many to a Transactions table (which would seem to be
the correct design)? If so, just add a new record to the Transactions
table using the MemberID; a Form based on Members with a subform based
on Transactions is convenient for this purpose.

If your table structure is different, please explain.

John W. Vinson[MVP]

 

[Guest]

No, I wasn't aware I needed a separate table for the transactions. So, I
think I would make a copy of the members table called "transactions" correct?
and the same with the members form? If that is indeed the case, how then to
make a one to many, which table would be on the right and left side? I'm
truely a beginner at this. Thank you.

 

[John Vinson]

No, I wasn't aware I needed a separate table for the transactions. So, I
think I would make a copy of the members table called "transactions" correct?

No.

A member is a member, and has attributes such as LastName, FirstName,
DateJoined, etc.

A Transaction is a different kind of entity; a transaction doesn't
have a last name but it has (I presume) a transaction date, and other
information about the transaction. Normally you would use a Form for
the "one" side (members?) with a Subform for the "many"; the "many"
side table would have a MemberID (but NO other member information).

and the same with the members form? If that is indeed the case, how then to
make a one to many, which table would be on the right and left side? I'm
truely a beginner at this. Thank you.

I don't know your business model, so I can't be sure; ask yourself
which sentence is correct:

Each Member can have many Transactions, but every Transaction pertains
to one and only one Member.

or

Each Transaction can involve many Members, but each Member is involved
in one and only one Transaction.

or

Each Member can have many Transactions, and each Transaction can
involve one or more Members.

These would correspond to One to Many Members -> Transactions; One to
Many Transactions -> Members; and the third to a many to many
relationship, which needs a third table.

Check out some of the introductory tutorials linked from these
websites; the Database Design 101 links on Jeff's webpage should be
particularly relevant.

Jeff Conrad's resources page:
http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html

The Access Web resources page:
http://www.mvps.org/access/resources/index.html


John W. Vinson[MVP]

 

[Guest]

Whew, I had no idea it was going to be that intense. Got a lot of reading to
do. But, basically, the third choice is what we need,

Each Member can have many Transactions, and each Transaction can

involve one or more Members.

While I'm doing my assigned research, could you also tell me the process,
step by step, on how to do this. I absorb like a sponge, and will be able to
use what you tell me to take on other projects, and as an adjuct to what I'm
reading.

Thank You
Most Sincerely.

 

[Guest]

Whew! I had no idea it would be so intense. I have a lot of reading to do.
Our need here is the 3rd model.

Each Member can have many Transactions, and each Transaction can

involve one or more Members.

While I'm doing my assigned reading (!), could you please tell me how to do
this, step by step, and I can use what you tell me as an adjunct to what I'm
reading. I absorb like a sponge, and can and will take what I learn to take
on other projects.

Thank You,
Most Sincerely.

 

[Guest]

Whew! I had no idea it would be so intense. I have a lot of reading to do.
Our need here is the 3rd model.

Each Member can have many Transactions, and each Transaction can

involve one or more Members.

While I'm doing my assigned reading (!), could you please tell me how to do
this, step by step, and I can use what you tell me as an adjunct to what I'm
reading. I absorb like a sponge, and can and will take what I learn to take
on other projects.

Thank You,
Most Sincerely.

 

[Guest]

Whew! I had no idea it would be so intense. I have a lot of reading to do.
Our need here is the 3rd model.

Each Member can have many Transactions, and each Transaction can

involve one or more Members.

While I'm doing my assigned reading (!), could you please tell me how to do
this, step by step, and I can use what you tell me as an adjunct to what I'm
reading. I absorb like a sponge, and can and will take what I learn to take
on other projects.

Thank You,
Most Sincerely.

 

[John Vinson]

Whew! I had no idea it would be so intense. I have a lot of reading to do.
Our need here is the 3rd model.

involve one or more Members.

While I'm doing my assigned reading (!), could you please tell me how to do
this, step by step, and I can use what you tell me as an adjunct to what I'm
reading. I absorb like a sponge, and can and will take what I learn to take
on other projects.

Thank You,
Most Sincerely.

It would help quite a bit if you could describe your information in a
bit more detail. What is a member? What are the relevant attributes
(chunks of information) that you need to know about a member? Same for
transactions? Is there any specific information (other than that a
transaction occurred) that you need to record when member X performs
transaction Y?

John W. Vinson[MVP]

 

[Guest]

Thank You, you were right, the information answered all my questions. And
gave me ideas on how to improve things.

Peace, Sean