On Wed, 31 May 2000, Helen Borrie wrote:

> At 06:47 AM 30-05-00 -0700, you wrote:
> >It looks like the problem is pretty simple. Your database is defined as
> >SQL dialect 3 -- and you are defining a "DATE" column. The message you
> >get is the one that means "there is a conflict in the understanding of sql
> >between dialect 1 and dialect 3" in something you've used.
> >
> >Your options are
> >- Recreate the database as a dialect 1 database.
> >- Use SQL dialect 3 exclusively (which may not be possible if you're using
> >BDE)
> >- Use TIMESTAMP instead of DATE (which you'ld have to do in sql dialect 3
> >anyway).
> >
> >Hope this helps
> >
> >Dave
>
>
> I pondered this DATE thing, too, and checked the IB 6 documentation. It
> says DATE is still supported. Is this a documentation bug, or has DATE
> changed to be 'date only' (i.e. no time incorporated now)?

I thought DATE in dialect 1 still means timestamp, and DATE in dialect 3
means date only. I think he was trying dialect 3, which wont work with
bde anyway,

randal

>
> Helen
>
> http://www.interbase2000.org
> ___________________________________________________
> "Ask not what your free, open-source database can do for you,
> but what you can do for your free, open-source database."
> (J.F.K.)
>
> ------------------------------------------------------------------------
> Was the salesman clueless? Productopia has the answers.
> http://click.egroups.com/1/4633/4/_/679568/_/959700348/
> ------------------------------------------------------------------------
>
> Community email addresses:
> Post message: IBDI@onelist.com
> Subscribe: IBDI-subscribe@onelist.com
> Unsubscribe: IBDI-unsubscribe@onelist.com
> List owner: IBDI-owner@onelist.com
>
> Shortcut URL to this page:
> http://www.onelist.com/community/IBDI
>