Check boxes select

  • Thread starter Thread starter ServiceEnvoy
  • Start date Start date
S

ServiceEnvoy

I need to know how to create an event so that when I click a check box
called "Cancelled" it will check several other boxes at the same time
(like "Billed", "Expensed", and "Completed"). How do I do this?
 
ServiceEnvoy said:
I need to know how to create an event so that when I click a check box
called "Cancelled" it will check several other boxes at the same time
(like "Billed", "Expensed", and "Completed"). How do I do this?
Click to expand...

create an AfterUpdate event procedure for 'Cancelled', and place the
following code in it:

With Me
.Billed = .Cancelled
.Expensed = .Cancelled
.Completed = .Cancelled
End With

That will ensure that Billed, Expensed and Completed echo the current status
of Cancelled, be it True or False (checked or un-checked).
 
Stuart's response is correct. His code will give you what you asked
for.

Now for the implications.

Billed and expensed are checked. Completed is not.

User ACCIDENTALLY checks Cancelled.
consequently all of them are now checked. But since it was an accident
the user now unchecks Cancelled.
Consequently now all of them are unchecked and the user has NO idea
what the proper settings for each should be.

Perhaps you should leave the other items exactly as they are and
change the criteria of anything that considers those flags to be
important to also look at the canceled flag and make the decision
appropriately.

Just adding food for thought. All the approaches are more or less
valid but they also all have implecations.

Ron
 
Stuart's response is correct. His code will give you what you asked
for.

Now for the implications.

Billed and expensed are checked. Completed is not.

User ACCIDENTALLY checks Cancelled.
consequently all of them are now checked. But since it was an accident
the user now unchecks Cancelled.
Consequently now all of them are unchecked and the user has NO idea
what the proper settings for each should be.

Perhaps you should leave the other items exactly as they are and
change the criteria of anything that considers those flags to be
important to also look at the canceled flag and make the decision
appropriately.

Just adding food for thought. All the approaches are more or less
valid but they also all have implecations.

Ron
Click to expand...

Hmmmmmm intersting food for thought. I'm open to any alternative
ways. Basically, I just want to make sure that when a call gets
cancelled that we don't have to go through and check every single
check box so that the call will not show up in our active calls lists
anymore. Can you offer another way to accomplish the same thing?
 
Change the query that pulls data for the active call lists to

NOT include items if the cancel flag is True (or cancelled date is not
null)

We have multiple applications that allow for cancel, but all active
lists check for the cancel flag. Also cancelled records is one of the
items that we keep statistics on. And we require a cancel reason and I
log a cancelled date and cancelled by.

And supervisors have the authority to re-activate a cancelled item.
And this allows us to pick up where we were and not re-invent the
wheel and gives us a better audit trail.

I don't know your system nor other implications, but if there are any $
$ values associated with billed and expensed, it would seem that
checking them off when they really haven't been done can lead to other
types of problems. Even if it was just trying to match record/action
counts, it would seem that just checking them off because it was
cancelled and not really expensed could lead to some other confusion.

This may be one of those 90/10 situations ( 90% of code for 10% of the
activity)

Hope this gives you some ideas (and not just nightmares).

Ron
 
Change the query that pulls data for the active call lists to

NOT include items if the cancel flag is True (or cancelled date is not
null)

We have multiple applications that allow for cancel, but all active
lists check for the cancel flag. Also cancelled records is one of the
items that we keep statistics on. And we require a cancel reason and I
log a cancelled date and cancelled by.

And supervisors have the authority to re-activate a cancelled item.
And this allows us to pick up where we were and not re-invent the
wheel and gives us a better audit trail.

I don't know your system nor other implications, but if there are any $
$ values associated with billed and expensed, it would seem that
checking them off when they really haven't been done can lead to other
types of problems. Even if it was just trying to match record/action
counts, it would seem that just checking them off because it was
cancelled and not really expensed could lead to some other confusion.

This may be one of those 90/10 situations ( 90% of code for 10% of the
activity)

Hope this gives you some ideas (and not just nightmares).

Ron
Click to expand...

Thanks. I'll play with it a little and see how the data turns out. I
think I have enough ideas to find a solution based on our needs.
 
Back
Top