Are you there Viv1! . . . . . .
Important!: Don't forget to backup the database before you make any changes!
If I understand you correctly you want:
1)The
default calculation(view) of Subscriptions_Balance to
always show reduction by Account_History!Total, with the
option of calculating without Account_History!Total and reverting back? Is this correct?
If the above is correct, will you need the option for the current member record, all members, or both? I suggest all members (I believe this is what you want) with two command buttons for calculations; one for Subscriptions_Balance with Account_History!Total, and one without(any payments automatically update the balance). If you require both, then I suggest an additional form be made to select the options. The opening of this form can triggered by many things . . . . a command button or double-clicking the Subscriptions_Balance control . . . for instance, or an option group could be added to select current record or all.
2) To order the recordsource for Account_History by Payment_Date Decending?
This is easy. Just make a query with the same fields, set the sort field to decending and change the Recordsource property for the form to the query.
3) To store the values used to calculate the balance.
We will get to this if we can get past the two above(they need to be done first). A big problem here is that you don't know what was used for all current records in the database. Aside from that, be assured they can be saved as well as the check combo and formula used.
Elaborate on these things well, as
your designing a part of your interface here . . . . and this is how its going to work!
a) are the Fees & EC_Fees tables, look-up tables?
b) Your description of the Account_History tables leads me to believe its involved in a One-To-One relationship via MembershipNo. Is this true?
c) Is Account_History a subform on the Members form?
To get a better Idea of whats going on in your database and to resolve what appears may be relationship problems, please post(if your not going to break any proprietary laws) all table relationship pairs using the following format. Note: look at the Relationship Window when you gather this info. IF a relationship link does not show the typical 1 to many identifiers, right click the link & select edit. At the bottom of the window that opens is the type of relationship.
TableName!PrimaryKeyName > 1 to Many > TableName!ForeignKeyName
TableName!PrimaryKeyName > 1 to 1 > TableName!PrimaryKeyName
Code:
Communication
-------------
In an attempt to enhance our communications and
hopefully provide help of another kind . . . . You have a great tendency to over complicate things Viv, to the point it all seems so overwhelming to you. If you simply state what you want without all the where's & whys, you will be more to the point, specific, and less confused. Let the other party ask for more specifics if required.
For instance: I want a table sorted by date, decending. Simple . . . to the point . . . . specific. I can say the same thing after explaining the complexity of a database(one or more paragraphs) and one reading it, would be totally confused by the time they got to the end and miss the point! . . . . . . . . see what I mean!
Relax . . . . . . . your in good hands . . . . . . .[/code]
TheAceMan