Calculating Time for clock's preset

[skimask]

Well, you never specified that you were using a 16Fxxx, so I guess you don't get to use a LONG variable.
And it's not so much if the 16F supports 32 bits, 'cause none of the 10F/12F/16F/18F support 32 bit variables. It's the compiler that either supports them or doesn't.

If its not related to the PIC then why can't I ?
According to this http://www.microchip.com/stellent/id...cName=en532453
what does the 32 means if not supporting 32-bit ?

With any luck, this should clear it up a bit...
PBP is a COMPILER....MPASM is an ASSEMBLER.
PBP supports...PICxxxxx (see their website...way too many to list)
MPASM supports...well, basically, anything in the Microchip inventory.
The PIC32 is supported by MPASM, the assembler.
The PIC32 isn't supported by PicBasicPro, the compiler.
A program is written (source code), is compiled (by PBP) into assembly code (machine code), and assembled (by MPASM) into hex code (binary to be programmed) by the programmer (PICKIT2 for example).

[amgen]

once started or stopped, start looking for the next event starting with hour = then min = then second > as DT suggested earlier if then.....
same logic a human would use looking for an event

amgen

[menta]

So where is it possible to use Long variables?

[amgen]

not needed, set up 1307 for 24 hr mode

[skimask]

So where is it possible to use Long variables?

PIC18Fxxxx and PBP...just like I said....just not so many words...