touble with a time calculation

[longpole001]

EL2_Allow is a Var bit , atm , and that code would require it to become VAR byte , i am getting very full on this chip and every byte less in mem is a good move ,

i am thinking since the value i am looking for is either 0 or 1 , can i leave the variable as a BIT , even though values higher than 1 are going to occur ?

[EarlyBird2]

EL2_Allow is a Var bit , atm , and that code would require it to become VAR byte , i am getting very full on this chip and every byte less in mem is a good move

Tight for space is a very good reason to make the code more efficient.

Obviously you have a routine that sets the time could you set the EL2_Allow and other "flags" within that code. I am thinking that at present the same comparisons are made multiple times in different places.

I am also led to believe that compound statements are inefficient.

EL2_Allow =  0
EL2_Allow =  EL2_Allow + Event1_OT_Day
                    EL2_Allow + Event1_OT_hour 
                    EL2_Allow + Event1_OT_Min         ' if all values are 0 , then don't enable the overrun timer 
                    EL2_Allow + Event1_OT_sec 
                    EL2_Allow + Event1_OT_100th

is more efficient than

EL2_Allow =  Event1_OT_Day + _
                    Event1_OT_hour + _
                    Event1_OT_Min + _            ' if all values are 0 , then don't enable the overrun timer 
                    Event1_OT_sec + _
                    Event1_OT_100th

can you explore this idea by trying both ways. This is food for thought for both of us which is very interesting.