In that case I think I'd go with the concatenation option: DATE()"R%5" : TIME()"R%5"
At least that'll get you up to October 14, 2241. Hopefully by then barcodes will have been replaced by telepathy. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com ** Check out scheduled Connect! training courses at http://www.PrecisOnline.com/train.html. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of George Gallen Sent: Wednesday, September 13, 2006 8:19 AM To: [email protected] Subject: RE: [U2] Time/Date as a single number yes. It needs to be to the second. My final solution at present, is to use 01/01/2006 as my base for the date, use the date*86400+time encoding, with my other manipulations, this will give me a span of about 12 years, and if this system is still in place in 12 years without being upgraded...well. My other option, is to shrink the barcode size to allow for more room, but right now, it's pretty small to begin with, and I'd rather not make it unscanable. For those asking, it's a code128 barcode subset C. The barcode doesn't need the checksum, but rather the other side does, which I have no control over, except for the definition of the number, but the checksum is still required. George > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Steve Johnson > Sent: Tuesday, September 12, 2006 6:12 PM > To: [email protected] > Subject: Re: [U2] Time/Date as a single number > > > George, > > Do you need to be accurate to one second? If you can live with > 10-second precision you can save one digit. > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
