I'm having a problem with my queries that use date
fiels. In Access, I have to put # around the date in my
SQL statements. This works great on my development
computer for Access, MSDE and SQL Server. My problem
comes up with I run my product on a workstation. It is
giving me a -2147418113 Catastrophic Error on my sql
statement. If I change the # to ' it works.
Why does it work on my development computer but not on a
different PC? My initial guess was because of a
different DLL that is installed on my PC.
Does anyone have any ideas?
hi Jeff,
"Jeff" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:97b801c49738$7abc4ca0$a601280a@.phx.gbl...
> I'm having a problem with my queries that use date
> fiels. In Access, I have to put # around the date in my
> SQL statements. This works great on my development
> computer for Access, MSDE and SQL Server. My problem
> comes up with I run my product on a workstation. It is
> giving me a -2147418113 Catastrophic Error on my sql
> statement. If I change the # to ' it works.
> Why does it work on my development computer but not on a
> different PC? My initial guess was because of a
> different DLL that is installed on my PC.
> Does anyone have any ideas?
I actually do not know, but, as you already stated, date have to be enclosed
in ' for SQL Server statements... and should raise an exception at parse
time otherway..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
No comments:
Post a Comment