Gustav Brock
Gustav at cactus.dk
Sun Apr 1 12:03:08 CDT 2007
Hi John But isn't the upsize thingy an Access tool? This SQL should cause zero problems: insert into dbo_timetable (timefield) values (#12:00:00 AM#) Which "other date problems" did you encounter? The datetime data type of Access/JET is very strict on holding valid dates/times only. This sounds very weird. /gustav >>> jwcolby at colbyconsulting.com 01-04-2007 18:46 >>> It is valid in ACCESS, but may not be in SQL SERVER. Or, as you say, it may be a limitation of the upsize wizard. All I know is that once I handled these (and other date problems) the table moved. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Sunday, April 01, 2007 8:10 AM To: accessd at databaseadvisors.com Subject: Re: [AccessD] SQL Server - Time only in date field Hi John That is strange - or it may be a limitation in the upsize wizard - as #12:00:00 AM# is a perfectly valid date value in Access. /gustav >>> jwcolby at colbyconsulting.com 01-04-2007 13:54 >>> In fact my question was more simple than that. I have values in the date fields that are #12:00:00 AM# for example. Those values are NOT valid in SQL Server, or at least will not upsize correctly. I had to find and fix all such values by adding some date to them to make them #1/1/1800 12:00:00 AM#. Once I did that, the table with such fields would upsize. John W. Colby Colby Consulting www.ColbyConsulting.com