Jacky Luk wrote:Second Scenario is to let them have a check box in each row for these
"sparse" purchasing customers, when it is done, they check the checkbox of that row.
But I really want to go for batch mode, which doesn't seem to be a good consistent method at all by human
factor.
Your intuition about "batch mode" not being the correct approach in this case seems to me to be a good intuition. What's going to be involved in this follow-up? My guess: the sales person will at some point in time call the customer and inquire about why they haven't been buying anything lately, and then try to persuade them to start buying again. I can tell you from experience that sales people don't like doing that, so it might not get done right away. (At one place where I worked, new hires were given a list of such customers and told to cold-call them and try to get new business out of them.) At any rate it's going to be a time-consuming process so you aren't going to have a lot of "Follow-up Completed" transactions. So yes, updating the "Follow-up Completed" flag (or date, or whatever) should probably be done one flag at a time.
(Of course I don't know all about your application, so I might be wrong. Perhaps you have a boiler room full of people calling ex-customers, for example.)
And yes, your system should allow for the situation where the sales person is told to follow up on a customer, but by the time the follow-up happens (or is recorded) the customer has placed a new order. If your current design results in a confused state when that happens, then I would say the design needs to be changed.