Vinay Kannan wrote:
Currently the DB structure stores the following : 1) Customer details. 2)
Membership ID and the payment paid at the time of signing up (I am thinking
i might not need the signing up amount to be stored in the customer DB in
the first place, and have them seperate in a table
I am working on an appplication with a Billing Module. The customers will
pay in the following manner. 1) Signing up Fees, at this time they will
choose they payment intervals, monthly, quaterly, 6 months or annual.
2) A customer can also change the billing type at a later time, Eg: after
paying
