Design the Student Payment or Student Fees

Question

0.00/5 (No votes)

See more:

I designing a system where it will be used in the tutoring, the tutoring will be teach: Mathematics, English, Physic and Mandarin. I already designed the students registration, editing the students info or deleting the students info. But, I couldn't come up with the idea on how to design the students fee. (e.g: The Student Name "Kaoru" with the Student ID "TP024836" wants to pay his bills for month "January 2014", and the fee is $50 per month). How could I design like this? Should I design manually on Access Database, or I design it on Windows Forms and Insert it to Access Database and display it on DataGridView? And what components that I have to provide in order to achieve this student payment? Thank you.

Best Regards

Posted 2-May-14 0:15am

Member 10192100

Updated 2-May-14 0:20am

Richard MacCutchan

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2014-05-02T00:25:00

Probably a combination of the two: you certainly need a database element to record payments, and you probably need to include payments owed in that table.

But you probably want to include WinForms to enter the payment, and to add the "new" debts to the system at the appropriate time.

So what I'd do is play with it on paper, with a pencil. Try to handle the payments (and remember there could be deferments, pre-payments, overpayments, and underpayments as well as correct ones) on paper and see what you need. When you have a paper system that works, it should be pretty obvious what is DB and what is WinForms, and what you need to do from there.