Re: [WebDNA] Storing time in 24hr format

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113053
interpreted = N
texte = 641 --001a11c16510d1d370053e59eced Content-Type: text/plain; charset=UTF-8 Hi Dale, I've built three different timeclock systems over the years.... I echo Kenneth, convert the real time format into the WebDNA time format for storage, and then convert it back again when you need to display it. You can do so much more with the data when it is stored this way. Take a look at this page for some useful hints: http://www.euca.us/admin/tests/sectodays.html BEst of luck, sfb Stephen F Braun sbraun1@twcny.rr.com On Fri, Oct 7, 2016 at 6:50 PM, Kenneth Grome wrote: > Maybe you ought to store times in WebDNA's default format. Then > you can deal with it more easily later, for example if you want to > change its web page display. > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration > > > On 10/07/2016 02:40 PM, dale wrote: > > Hi all, > > > > I am going to be storing shirt start and shift end times in a db. > > For now it is simply showing when the technicians are scheduled to > > start and end their shift as well as when their lunch time starts. > > > > I'm not looking for code, only your thoughts on the smartest/most > > flexible way to save the time. > > > > For doing any calculations I may need or want to do later, would > > you recommend storing the time as: > > > > 6:00 > > 06:00 > > 0600 > > > > > > I believe the later is the correct representation of 24 hour time. > > And probably would be easier to do any math on the numbers. > > > > > > For a further revision, I have been asked to look into eventually > > using this site as a time clock to replace the system we are > > currently using. These punch-in times and dates will be stored in > > another database. The majority of the techs start work about 6:00 > > pm and work until 3:00am. > > > > The above data will also include location information from their > > mobile devices (they all work on various lots, so location > > information is important). > > > > Thank you for your thoughts. > > > > Dale > > --------------------------------------------------------- This > > message is sent to you because you are subscribed to the mailing > > list . To unsubscribe, E-mail to: archives: > > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > > support@webdna.us > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --001a11c16510d1d370053e59eced Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Dale,
I've built three different timeclock syst= ems over the years....
I echo Kenneth, convert the real time form= at into the WebDNA time format for storage, and then convert it back again = when you need to display it.
You can do so much more with the dat= a when it is stored this way.

Take a look at this = page for some useful hints: =C2=A0 =C2=A0http://www.euca.us/admin/tests/sectodays.html

BEst of luck,
sfb




Stephen F Braun
sbraun1@twcny.rr.com=

On Fri, Oct 7, 2016 at 6:50 PM, Kenneth Grom= e <ken@webdnasolutions.com> wrote:
Maybe you ought to store times in WebDNA's default for= mat.=C2=A0 Then
you can deal with it more easily later, for example if you want to
change its web page display.

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Administration


On 10/07/2016 02:40 PM, dale wrote:
> Hi all,
>
> I am going to be storing shirt start and shift end times in a db.
> For now it is simply showing when the technicians are scheduled to
> start and end their shift as well as when their lunch time starts.
>
> I'm not looking for code, only your thoughts on the smartest/most<= br> > flexible way to save the time.
>
> For doing any calculations I may need or want to do later, would
> you recommend storing the time as:
>
> 6:00
> 06:00
> 0600
>
>
> I believe the later is the correct representation of 24 hour time.
> And probably would be easier to do any math on the numbers.
>
>
> For a further revision, I have been asked to look into eventually
> using this site as a time clock to replace the system we are
> currently using. These punch-in times and dates will be stored in
> another database. The majority of the techs start work about 6:00
> pm and work until 3:00am.
>
> The above data will also include location information from their
> mobile devices (they all work on various lots, so location
> information is important).
>
> Thank you for your thoughts.
>
> Dale
> --------------------------------------------------------- This > message is sent to you because you are subscribed to the mailing
> list . To unsubscribe, E-mail to: archives:
> http://mail.webdna.us/list/talk@webdna.us Bug= Reporting:
> support@webdna.us
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@web= dna.us>.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://ma= il.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --001a11c16510d1d370053e59eced-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Storing time in 24hr format (dale 2016)
  2. Re: [WebDNA] Storing time in 24hr format (Donovan Brooke 2016)
  3. Re: [WebDNA] Storing time in 24hr format (christophe.billiottet@webdna.us 2016)
  4. Re: [WebDNA] Storing time in 24hr format (Stephen Braun 2016)
  5. Re: [WebDNA] Storing time in 24hr format (Kenneth Grome 2016)
  6. Re: [WebDNA] Storing time in 24hr format (dale 2016)
  7. Re: [WebDNA] Storing time in 24hr format (Donovan Brooke 2016)
  8. [WebDNA] Storing time in 24hr format (dale 2016)
641 --001a11c16510d1d370053e59eced Content-Type: text/plain; charset=UTF-8 Hi Dale, I've built three different timeclock systems over the years.... I echo Kenneth, convert the real time format into the WebDNA time format for storage, and then convert it back again when you need to display it. You can do so much more with the data when it is stored this way. Take a look at this page for some useful hints: http://www.euca.us/admin/tests/sectodays.html BEst of luck, sfb Stephen F Braun sbraun1@twcny.rr.com On Fri, Oct 7, 2016 at 6:50 PM, Kenneth Grome wrote: > Maybe you ought to store times in WebDNA's default format. Then > you can deal with it more easily later, for example if you want to > change its web page display. > > Regards, > Kenneth Grome > WebDNA Solutions > http://www.webdnasolutions.com > Web Database Systems and Linux Server Administration > > > On 10/07/2016 02:40 PM, dale wrote: > > Hi all, > > > > I am going to be storing shirt start and shift end times in a db. > > For now it is simply showing when the technicians are scheduled to > > start and end their shift as well as when their lunch time starts. > > > > I'm not looking for code, only your thoughts on the smartest/most > > flexible way to save the time. > > > > For doing any calculations I may need or want to do later, would > > you recommend storing the time as: > > > > 6:00 > > 06:00 > > 0600 > > > > > > I believe the later is the correct representation of 24 hour time. > > And probably would be easier to do any math on the numbers. > > > > > > For a further revision, I have been asked to look into eventually > > using this site as a time clock to replace the system we are > > currently using. These punch-in times and dates will be stored in > > another database. The majority of the techs start work about 6:00 > > pm and work until 3:00am. > > > > The above data will also include location information from their > > mobile devices (they all work on various lots, so location > > information is important). > > > > Thank you for your thoughts. > > > > Dale > > --------------------------------------------------------- This > > message is sent to you because you are subscribed to the mailing > > list . To unsubscribe, E-mail to: archives: > > http://mail.webdna.us/list/talk@webdna.us Bug Reporting: > > support@webdna.us > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > --001a11c16510d1d370053e59eced Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Dale,
I've built three different timeclock syst= ems over the years....
I echo Kenneth, convert the real time form= at into the WebDNA time format for storage, and then convert it back again = when you need to display it.
You can do so much more with the dat= a when it is stored this way.

Take a look at this = page for some useful hints: =C2=A0 =C2=A0http://www.euca.us/admin/tests/sectodays.html

BEst of luck,
sfb




Stephen F Braun
sbraun1@twcny.rr.com=

On Fri, Oct 7, 2016 at 6:50 PM, Kenneth Grom= e <ken@webdnasolutions.com> wrote:
Maybe you ought to store times in WebDNA's default for= mat.=C2=A0 Then
you can deal with it more easily later, for example if you want to
change its web page display.

Regards,
Kenneth Grome
WebDNA Solutions
http://www.webdnasolutions.com
Web Database Systems and Linux Server Administration


On 10/07/2016 02:40 PM, dale wrote:
> Hi all,
>
> I am going to be storing shirt start and shift end times in a db.
> For now it is simply showing when the technicians are scheduled to
> start and end their shift as well as when their lunch time starts.
>
> I'm not looking for code, only your thoughts on the smartest/most<= br> > flexible way to save the time.
>
> For doing any calculations I may need or want to do later, would
> you recommend storing the time as:
>
> 6:00
> 06:00
> 0600
>
>
> I believe the later is the correct representation of 24 hour time.
> And probably would be easier to do any math on the numbers.
>
>
> For a further revision, I have been asked to look into eventually
> using this site as a time clock to replace the system we are
> currently using. These punch-in times and dates will be stored in
> another database. The majority of the techs start work about 6:00
> pm and work until 3:00am.
>
> The above data will also include location information from their
> mobile devices (they all work on various lots, so location
> information is important).
>
> Thank you for your thoughts.
>
> Dale
> --------------------------------------------------------- This > message is sent to you because you are subscribed to the mailing
> list . To unsubscribe, E-mail to: archives:
> http://mail.webdna.us/list/talk@webdna.us Bug= Reporting:
> support@webdna.us
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@web= dna.us>.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://ma= il.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us --001a11c16510d1d370053e59eced-- . Stephen Braun

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

[WebDNA] v7 Stress Test and Strange Behaviour (2012) WebCat2 - Getting to the browser's username/password data (1997) emailer w/F2 (1997) I give up!! (1997) [BULK] [WebDNA] [BULK] WebDNA 7 - Ready or Not ?? I'm not sure... (2011) Date formats and sandboxes (2004) [WebDNA] v7 thisurl has different behavour (2012) Authorize.net SIM/AIM deadline extended (2003) PCS Frames (1997) [OT] WebDNA Training (UK) (2003) [protect admin] (1997) Siteedit (1999) Webcat/Webmerchant part II (1998) looping table rows (1999) auto adding SKUs w/DB helper (1998) Encrypt question. (2000) TaxTotal (2003) SMSI -- a [notfound] context? (2002) summ=T (2003) Getting Total Quantity (1997)