|
|
Posted by <david on 10/31/05 04:48
Obscure footnote:
> any floating point columns in your data (including
> datetime as these are stored as floating point numbers)
SQL Server doesn't store datetime as double. Access does,
and the problem arises because of the rounding error in
the conversion between the Access version and the SQL
Server version, even when values are not 'stored' in Access
at all.
(david)
"Trevor Best" <nospam@localhost.invalid> wrote in message
news:43656dd0$0$345$da0feed9@news.zen.co.uk...
> Neil wrote:
..>
> I've not had any problems with Host_name() as a parameter, as the only
> records I retrieve are for my particular machine there is very little
> point in returning that column so I never ask the server for it as I
> know the value already.
>
> A couple of things you need to know about Access and SQL Server, firstly
> bit fields should be made NOT NULL and default to 0 as Access interprets
> these as Jet Yes/No columns and treats them accordingly so it expects a
> value to be there (In Access/Jet, a Yes/No column cannot be null and
> defaults to 0). The results otherwise can be unpredictable.
>
> Secondly, if you have any floating point columns in your data (including
> datetime as these are stored as floating point numbers) then you most
> probably need a timestamp column as floating point errors can cause the
> #Deleted condition you describe.
Navigation:
[Reply to this message]
|