Viescas membership database multiple member rates???

[tlyczko]

Hello,

I have John Viescas' excellent book 'Building Access Apps' and the
membership app is great, but it does not permit having multiple
membership rates, such as Individual at $5.00, Business at $10.00, etc.

I think it should be possible for me to figure out implementing this
but I don't want to break the actual design per se too much...

Has anyone implemented this?? If so, did you do it with just a lookup
table, etc. and how did you track rate changes (this is not as
important to me really as having multiple membership types at different
rates)??

Thank you,
Tom

 

[John Viescas]

Tom-

The application already handles multiple dues rates - for different time
periods. You could add a DuesType field to the tblDuesRates table, make it
a part of the Primary Key, and then modify the frmDuesRates form to edit
this additional field. You might want to add a lookup table to describe and
limit the different types of dues.

You'll also need to modify fsubMemberDues and fsubMemberAttendDues to handle
the new field - and change the validation code in those forms as well.

Does that help?

John Viescas, Author
"Building Microsoft Access Applications"
"Microsoft Office Access 2003 Inside Out"
"SQL Queries for Mere Mortals"

 

[tlyczko]

Hello John,

Thanks a lot for taking time to reply...I will study your response and
db tables etc. based on what you said here.

I think your recommendation will work if I just use different arbitrary
'periods' for each rate and dues type.

The other mods you mention should not be too hard.

I already thought of adding a DuesType field, but wasn't certain about
getting the rate variations, etc., thank you for helping break my
mental logjam. I assume the lookup table you mention would be like the
other lookup tables you created, and I can copy the basic concept.

Thank you,
Tom

 

[PC Datasheet]

You need the following tables:
TblMembershipType
MembershipTypeID
MembershipType

TblMembershipRate
MembershipRateID
MembershipTypeID
MembershipRateAsOfDate
MembershipRate

 

[tlyczko]

Thank you, PCD...tblMembershipType can be covered by another table in
the database, called tblStatus, which does essentially the same thing.
I will look at your idea of tblMembershipRate, which is similar to his
tblDuesRates table.

Thank you,
Tom

 

[tlyczko]

Hello, I am still reading your book, I will have to read it all several
times.

Will the sample databases you included successfully handle 2 to 5
concurrent users??

If my agency wants to go beyond your database, they'll need serious
fundraising/membership software anyway...

Thank you,
Tom

 

[John Viescas]

Tom-

Three of the sample databases (including Membership) are designed to support
up to 20 concurrent users. The fourth one that uses unbound forms can
handle 50 or more.

John Viescas

 

[tlyczko]

Hello John,
Thank you for replying!
20 is plenty, thank you!
I just now have to learn how to apply your recommendations and how to
set up something for permissions as to who can do what with the app.
Thank you,
Tom