Well Thanks for all the feedback. I thought I had figured it out using
a combination of various pieces from everyone who posted to the
questions. But again, it wasn't working ... I had one script working and
another that wasn't ... what the [EMAIL PROTECTED] Anyway, "I think" I've figured
out what the problem is. Ya, its annoying as hell. At this point I'm
assuming that the whole "#" thing for Date/Time fields is really for
Micorosoft centric technologies such as ASP. But for Perl & DBI/DBD
used with Access the problem was seemingly bizarre because I had
multiple problems. The cdate('$dt') function works .... and so does
this other format method {ts '2010-10-11 07:07:07'} ... but also does
simple single quotes as Tim suggested. As it turns out what was really
nailing me is that the field name has a lot to do with it. I originally
had the Date/Time field named "TimeStamp" which doesn't work, I have
also tried DateTime which doesn't work, dt worked which was why my
simple prototype worked while my app didn't, Date_Time works .... so
apparently I can't pick a decent field name. Funny thing is, this was
someone else's database I usually don't use Upper Case at all. So, I'm
going to rename all these TimeStamp fields and hope for the best. I
hope the next project is a MySQL one! Any additional info would be
appreciated immensely.
$dt = "4/14/2005 23:10:57 PM";
$sql = "UPDATE tblTest SET name = 'Robb', dt = cdate('$dt') WHERE id = 1";
$sql = "UPDATE tblTest SET name = 'Robb', Date_Time = {ts '2010-10-11
07:07:07'} WHERE id = 1";
my $sql = "UPDATE tblUser SET EmailAddress = '$newemail', Date_Time =
'$dt' " .
"WHERE Password = '$password'";
TimeStamp < ---- BAD
DateTime <---- BAD
Robb
