I said "And, for checking due date, run a routine once a day and print a report. A field in a configuaration file can store last_due_date_check. If it is less than today, run the procedure." I was suggesting that you do this automatically when you run the system. That was the point of the configuration file and the field storing the last date it was run. That way it will only be run once a day. You run it and replace the field with the current day. Then it will only be run once a day at most. The problem with this is if the customer doesn't exit the system and because the routine is only run when the system is loaded. With most people, this isn't a problem as they load programs daily at least.

What was the answer about Outlook and running over midnight?

The whole thing is this: Pick when you want it to be run and do it. It doesn't make sense to do it many times a day.

Also John, in your first message you talked about a credit limit, which is usually a dollar amount. Now you are talking about when a limit is due. That sounds like a date. Could you please clarify what you want?

And what is wrong with running whatever it is you want once a day if it is to do with a due date? And if it is to do with hitting a credit limit, do it (as I suggested before) at times when a credit limit can be exceeded. Please let me know what the problem is.


>that's exactly right. but my customre is not wanted that way. he does not want to remember to run routine daily and take report. according to him automatically
>system should give him warning that such customer's limit is due so he will go and look at my file and print if he wanted.
>he has seen this in outlook and he urges same requirement here in database application. but i think i have come to conlusion that the required functionality is not a good idea. and let the customer to run routine to get what he wants.
>what you guys say? still welcome any suggestions.
>thanksverymuch
>john still