Subject | [IBO] Re: SQL-dialect 3 instead of 1? |
---|---|
Author | guido.maucher |
Post date | 2007-02-12T14:12:48Z |
The last error I mentioned - removing old IBObjects directory - showed
me my error. Not IBO 4.7 beta 11, but IBO 4.5 was used in the compiled
version.
No everything is working fine with dialect 1. And the tests for
dialect 3 yields to the expected error 'DATE' instead of 'TIMESTAMP'.
Thanks to all for the help.
Guido
me my error. Not IBO 4.7 beta 11, but IBO 4.5 was used in the compiled
version.
No everything is working fine with dialect 1. And the tests for
dialect 3 yields to the expected error 'DATE' instead of 'TIMESTAMP'.
Thanks to all for the help.
Guido
--- In IBObjects@yahoogroups.com, "Alan McDonald" <alan@...> wrote:
>
> > Hello Alan,
> > the SQL statement is a simple insert with a "string" instead of
> > 'string' - therefore a problem with dialect 3.
> > But after recognizing that it is only my problem, I installed this
> > morning IBObjects build 16 on a third computer, compiled the same
> > sources and made the tests - no problem!
> > So it is not IBObjects! But it seems to be a setting during
> > compilation on my computer !?
> > No idea which one - but I keep on finding it....
> > Thanks for the help
> > Guido
>
> This sounds very relevant now. Could it be that you are using double
quotes
> which are interpreted by Dialect 3 as an object delimiter but in
Dialect 1
> it is equivalent to using single quotes?
> Alan
>
> > > > Hello Alan,
> > > > ok, it looks as the problem is only my problem. What is the
problem:
> > > > I made a test with dialect 3 to see what will be the problems
using
> > > > this dialect. One of my SQL-statements failed with:
> > > > Dynamic SQL Error
> > > > SQL error code = -804
> > > > Count of read-write columns does not equal count of values
> > > >
> > > > Our database software project is on a server in the network.
> > > > Compiled with a computer having IBO beta 11, copied the
executable to
> > > > my pc the application works fine.
> > > > But compiling the same sources on the net with my computer -
now with
> > > > build 16 - I'm getting the error written above. Same as during the
> > > > tests with dialect 3, therefore the assumption it might be a
dialect
> > > > problem...
> > > >
> > > > Any idea what is going wrong?
> > > > Thanks
> > > > Guido
> > >
> > > I think it would help a lot if you showed us the SQL statement in
> > question
> > > don't you?
> > > Alan
>