[AccessD] Problem With Ageing Function Further to.....

Thanks for the replies Stuart and Gustav.....

Of course you were right Stuart it WAS working ...After your reply I tried 
it again with one difference ...I put the date as a string (as you did) 
"01/01/2006" instead of a date #01/01/2006# and it worked fine .....I havent 
tried again as a date so I dont know whether that was a problem or maybe the 
moon was in the wrong plain or my coffee supply was too low . I actually 
have a suspicion that the test data I was using was all 12 months old which 
would probably explain why all my ageing came out at 90 days.... as I said 
.......stupid

So now my function works exactly as it should but now brings another 
problem.......

I am using the function in an update query to update the customers 
transaction file aging wise on the fly as he is accessed, the result is then 
displayed in a list box on my customer form and also will be used in a 
statement report once I build it. The UNFORSEEN problem I now have is ......

Say a customer owes a total of $400 which has been incurred over the last 4 
months so
current = $100
30day = $100
60day = $100
90day = $100

He now pays his account in total in the current month so....
current = $-300
30day = $100
60day = $100
90day = $100

My transaction file is simply invoices as positive amounts and cheques and 
payments as negative amounts so that the total result is what is owing. How 
would you normally handle a situation like this. the result is actually 
accurate but of course this is not how you would display it.....

As usual any help is appreciated

Regards
Tom Keatley