[AccessD] Seconds Missing

If it were I in your place, I would look instead at defaulting the
datetime column in the SQL table to GetDate(), which will grab the
system dateTime for you. Then you can direct your concerns to the data
other than this column. I use this technique all the time and forget
about the Access equivalents. What I care most about is when the row was
inserted, so I'd leave it to SQL to determine that.

Arthur

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Michael
Brösdorf
Sent: Monday, July 19, 2004 9:18 AM
To: Access Developers discussion and problem solving
Subject: AW: [AccessD] Seconds Missing


Does it work if you enter a time including seconds directly into the
linked table?

If so, I would try to track down the problem using the Profiler from SQL
Server. Run the append query while Profiler is running to find out what
exactly is sent to the server.

Comparing date/time-values is always a problem with Access and
SQL-Server, because date and time are always stored as ONE number. I've
come to the point where I explicitly convert any data/time-value to a
string ("20041231", "1755") before I do the comparison. This way you can
also solve the problems that might result from the different base-dates
used in SQL Server and Access.

Michael