jwcolby
jwcolby at colbyconsulting.com
Sat Apr 2 13:19:14 CDT 2011
As it turns out, it is a driver issue. Using vanilla ODBC rather than the native SQL Server causes the (data entry) issue to go away. John W. Colby www.ColbyConsulting.com On 4/2/2011 12:49 PM, Gustav Brock wrote: > Hi John > > That should influence the fractions of a second only: > > http://msdn.microsoft.com/en-us/library/bb677243.aspx > Specifies the number of digits for the fractional part of the seconds. > This can be an integer from 0 to 7. > The default fractional precision is 7 (100ns). > > As Access out of the box doesn't support fractions of seconds, you must be facing another issue. > > /gustav > > >>>> jwcolby at colbyconsulting.com 02-04-2011 17:37:07>>> > What does the (7) really mean? Is it possible to manipulate that number to determine how many > seconds / milliseconds etc that SQL server is expecting to be entered? > > Im am trying to enter time in Access and I am currently required to enter the seconds part > > hh:mm:ss > > 08:00:00 > > If I don't enter the seconds SQL Server complains as I try to store the field. > > >