The only window of confusion that I am aware of is if there is some code
that is execute prior to actually establishing a connection such that the
SQL Dialect can be known. I didn't want to make it force the database open
just to get the SQL Dialect. Is the connection connected? if not, try making
it connect before running the suspect part of your application.

Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Claudio Valderrama C." <cvalde@...>
To: <IBObjects@egroups.com>
Sent: Thursday, January 04, 2001 7:59 PM
Subject: RE: [IBO] Switching Dialects


> That's strange. IBO usually detects the dialect. Jason will have to look
> into this particular case.
> I still remember when I began bugging Jason to make him support dialect 3
> and quoted identifiers. ;-)
>
> C.
>
> > -----Original Message-----
> > From: James Bunting [mailto:jpb@...]
> > Sent: Jueves 4 de Enero de 2001 12:51
> > To: IBObjects@egroups.com
> > Subject: Re: [IBO] Switching Dialects
> >
> >
> > > You don't change the dialect this way. Dialect is actually
> > structural and
> > > tied to the dataset. The reason you can set that is if you were about
to
> > > call the CreateDatabase method.
> >
> > The database is a IB6 database and I can connect, but if I do the
> > query SELECT * FROM MYTABLE, I get an error saying:
> >
> > "Data type unknown. Client SQL dialect 1 does not support
> > reference to DATE datatype"
> >
> > However, I can do the same query using IBX and IBConsole and it
> > works. That's why I was trying to manual set the Dialect, as we are
> > using Dialect 3 data types.
> >
> >
> > James Bunting
> >
> > Systematic Marketing Ltd
> > http://www.systematicmarketing.com
> > http://www.ukindex.co.uk