That won't work.
You need a table with fields like this:
CustomerID (not customer name)
Separating the payments into separate records will allow you to chart the data as you want. You don't want to record payments by customer name because you might get two customers with the same name and then their payment records will be combined/confused with each other.
can have customer ID also as a field….
nevertheless each customer over time does multiple payments so the rest of the fields will remain the same. if i enter the payments of the same customer into separate accounts then each customer will have 20+record
Correct, you can end up with many payment records for the same customer. A commonly used method of recording/browsing and editing a set of related records is to use a portal. And that would easily fit the layout example you have posted here.
thanks phil....will get on to it and try to modify the dbase accordingly