<br><div class="gmail_quote">On 7 June 2012 21:42, Metzler, David <span dir="ltr"><<a href="mailto:metzlerd@evergreen.edu" target="_blank">metzlerd@evergreen.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div lang="EN-US" link="blue" vlink="blue">
<div>
<p class="MsoNormal"><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy">That sounds more feasible. Note that
drupal date and time fields are likely unix timestamps, so you my run into troubles
converting from access times to date times, but provided you can get that date
math to work out, it seems plausible. <u></u><u></u></span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial"><span style="font-size:10.0pt;font-family:Arial;color:navy"><u></u> <u></u></span></font></p>
<p class="MsoNormal"><font color="#000080" face="Arial"><br></font></p></div></div></blockquote><div><br></div><div>Thanks for your input David..</div><div><br></div><div>The "Date" module saves as a Datetime field so the format shouldn't be a problem.. Also the "clocking" interface is php based and the plan is to change the query to update the correct table..</div>
<div><br></div><div>Thanks again.. </div></div>