Question : Microsoft Access: Creating a payment system.

Hello,

I am creating a database for a sports club and our members can pay in the following ways:

1. Per visit.
2. For one month.
3. 3 month contract.
4. 6 months contract.
5. 12 months contract.

What I need to achieve:

1. To be able to see what contract a client is using.
2. To see if they have payed for the latest month or if the are in debt for 1+ months.
3. How many months are left to go on their contract.
4. Input monthly payments (Date, type (cash, credit card, direct debit etc.))
5. See if they have an active contract or if it has finished already.

So far I've got tables for:

Clients. (Client information)
Clubs. (Data for the 2 clubs that we have right now)
Contracts. (Type of contract, start date, end date, fee, active or not)
Payment. (Payment Date, Payment Fee, Payment Type)
Purchase type. (1 time card, 1 month card, 3 months contract, 6months contract. etc.)

Now then, I am not sure if this design is ok, and how should I tie this together in order for the system to work properly?

Best Regards,

NewSkol

Answer : Microsoft Access: Creating a payment system.

Well, one thing that might be an idea is to use the new database wizard in Access itself to see if any of the existing template database will help you out.

There's a template on Microsoft's website at http://office.microsoft.com/en-ca/templates/club-membership-database-TC001047743.aspx that you might want to look at.

Lastly, just Google for "club membership database" and see what's out there.  If your goal is to learn how to program in Access, then that's one thing.  If it's to handle the club membership, then don't go inventing any wheels!

(If it IS to learn Access, then check http://msdn.microsoft.com/en-us/office/dd547097.aspx.  My favorite books were a set: the Access Developer's Handbook (Desktop), Access Enterprise Developer's Handbook, and VBA Developer's Handbook.  They're for older editions of Access but the principles they cover are still relevant and solid.)

I've spent many years developing with Access, and my personal nightmare is dealing with a client I like, but who doesn't understand that they're asking me to take on a three month project to design and build a reliable system for them.  On one hand, they're used to going to Best Buy and getting Microsoft Office for a few hundred bucks in all it's glory, and on the other hand there's me telling them I'm going to charge them $25,000 to create their "little" application!  Ow!

I'm not ripping them off: I've got to analyze the business problem, design a solution, apply all the years of studying database theory, apply all my experience in the trenches, help them avoid pitfalls they won't have thought about, do so incrementally to make sure I don't do any redundant work, AND pay extortionate professional liability insurance!

So I'm available for specific questions, but general guidance is a minefield as it can step into a major commitment that I'm just not available to make.  

I hope that all makes sense.
Random Solutions  
 
programming4us programming4us