Menu
▾
▴
firebird-odbc-devel — All about development of Firebird ODBC driver donated by IBPhoenix
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(23) |
Sep
(6) |
Oct
(2) |
Nov
(2) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
|
Feb
(14) |
Mar
(16) |
Apr
(14) |
May
(25) |
Jun
(38) |
Jul
(22) |
Aug
(39) |
Sep
(3) |
Oct
(13) |
Nov
(47) |
Dec
(3) |
| 2003 |
Jan
(38) |
Feb
(39) |
Mar
(24) |
Apr
(57) |
May
(30) |
Jun
|
Jul
(39) |
Aug
(90) |
Sep
(41) |
Oct
(141) |
Nov
(158) |
Dec
(137) |
| 2004 |
Jan
(86) |
Feb
(169) |
Mar
(100) |
Apr
(83) |
May
(94) |
Jun
(77) |
Jul
(85) |
Aug
(54) |
Sep
(45) |
Oct
(36) |
Nov
(42) |
Dec
(70) |
| 2005 |
Jan
(46) |
Feb
(44) |
Mar
(50) |
Apr
(73) |
May
(90) |
Jun
(87) |
Jul
(41) |
Aug
(47) |
Sep
(28) |
Oct
(23) |
Nov
(44) |
Dec
(81) |
| 2006 |
Jan
(21) |
Feb
(9) |
Mar
(82) |
Apr
(14) |
May
(109) |
Jun
(175) |
Jul
(188) |
Aug
(44) |
Sep
(5) |
Oct
(47) |
Nov
(15) |
Dec
(34) |
| 2007 |
Jan
(75) |
Feb
(24) |
Mar
(30) |
Apr
(4) |
May
(28) |
Jun
(9) |
Jul
(13) |
Aug
(13) |
Sep
(29) |
Oct
(15) |
Nov
(19) |
Dec
(12) |
| 2008 |
Jan
(7) |
Feb
(19) |
Mar
(1) |
Apr
(7) |
May
(13) |
Jun
(19) |
Jul
(17) |
Aug
(29) |
Sep
(15) |
Oct
(37) |
Nov
(18) |
Dec
(29) |
| 2009 |
Jan
(23) |
Feb
(12) |
Mar
(8) |
Apr
(16) |
May
(11) |
Jun
(1) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(9) |
Nov
(17) |
Dec
(31) |
| 2010 |
Jan
(15) |
Feb
(5) |
Mar
(4) |
Apr
(8) |
May
(1) |
Jun
(5) |
Jul
(17) |
Aug
(2) |
Sep
(12) |
Oct
(33) |
Nov
(14) |
Dec
(24) |
| 2011 |
Jan
(11) |
Feb
(2) |
Mar
(34) |
Apr
(11) |
May
(12) |
Jun
(3) |
Jul
(6) |
Aug
(11) |
Sep
(10) |
Oct
(1) |
Nov
(8) |
Dec
|
| 2012 |
Jan
(16) |
Feb
(2) |
Mar
|
Apr
(2) |
May
(6) |
Jun
(2) |
Jul
(7) |
Aug
|
Sep
|
Oct
(7) |
Nov
(22) |
Dec
(2) |
| 2013 |
Jan
(1) |
Feb
(24) |
Mar
(15) |
Apr
(2) |
May
(3) |
Jun
|
Jul
(2) |
Aug
|
Sep
(2) |
Oct
(6) |
Nov
(10) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
|
Dec
(5) |
| 2015 |
Jan
(1) |
Feb
(4) |
Mar
(3) |
Apr
(3) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2016 |
Jan
(1) |
Feb
(9) |
Mar
(4) |
Apr
|
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(7) |
Nov
(13) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(12) |
Oct
(4) |
Nov
|
Dec
|
| 2018 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
(6) |
Jun
|
Jul
(9) |
Aug
(4) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
(1) |
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(3) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2025 |
Jan
|
Feb
(2) |
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Alberto S. <alb...@sy...> - 2002-03-20 11:41:14
|
I discovered IBPhoenix site a little while ago and I found that I'm not able to download the binaries (but also the sources) of ODBC drivers. I'm not sure that you are able or "titled" to answer to this but I can't found a better reference. Thanks for any answer. Alberto Alberto Sacchini SysComm.it srl tel./fax +39 0521 208820 http://www.syscomm.it/ |
|
From: Don K. <do...@ab...> - 2002-03-15 19:41:59
|
I was attempting to install the Firebird ODBC Driver on a Windows 2000 Machine and it blew up during the Installation. I received an error on a Windows 95 and a Windows NT machine but it seems like it installed OK. With the Windows 2000 machine I cannot see the Driver in the ODBC list. Any ideas? <<OdbcJdbc-20010711.zip>> Don |
|
From: Paul R. <pr...@ib...> - 2002-03-14 10:06:02
|
Jrgen Arndt wrote: > > In this moment, i stay a little bit confused witg the Open-Source Interbase > (STOPED) and > Firebird (go ahead). I Use the RAD tool DELPHI 6.0. Will Firebird service > native Drivers to Firebird or only by ODBC. How locks the future to service > the RAD tools DELPHI and C++ Builder and Kylix. > > I think this are question that is very important for me and i think for many > other people to. > Firebird does need its own dbExpress driver. However, somebody needs to write it. It is a fairly straightforward project. The code for the MySQL driver has been published. There is a lot of experience with writing to the Firebird API. But a months work is probably needed for a project like this. If anyone wants to take it on I believe that Firebird would happily include it as part of the project and provide help in writing and testing it. But it really needs someone to take charge, write most of the code and see it through to completion. It is something I'd like to do if I had the time, but that time just doesn't exist for me at the moment. Paul -- Paul Reeves http://www.ibphoenix.com taking InterBase further |
|
From: Jürgen A. <ar...@t-...> - 2002-03-14 09:23:49
|
Hallo, I get this information (lock the end of this page) from the community.borland.com. My question ist, gives dbExpress drivers for Firebid or there are 100% Compatible to the dbExpress InterBase 6.5 drivers for Delphi. And if there are not 100% Compatible with Firebird will Firebird build this drivers self for Delhp and C++ Builder? In this moment, i stay a little bit confused witg the Open-Source Interbase (STOPED) and Firebird (go ahead). I Use the RAD tool DELPHI 6.0. Will Firebird service native Drivers to Firebird or only by ODBC. How locks the future to service the RAD tools DELPHI and C++ Builder and Kylix. I think this are question that is very important for me and i think for many other people to. 12 Mar dbExpress InterBase 6.5 driver for Delphi 6 available The Delphi 6 registered users site now has the dbExpress driver for InterBase 6.5 12 Mar Additional dbExpress driver options John K culled a list of third-party drivers available for dbExpress from the dbExpress newsgroups, and has compiled it in this article. |
|
From: Jürgen A. <ar...@t-...> - 2002-03-14 09:23:26
|
Hallo, I get this information (lock the end of this page) from the community.borland.com. My question ist, gives dbExpress drivers for Firebid or there are 100% Compatible to the dbExpress InterBase 6.5 drivers for Delphi. And if there are not 100% Compatible with Firebird will Firebird build this drivers self for Delhp and C++ Builder? In this moment, i stay a little bit confused witg the Open-Source Interbase (STOPED) and Firebird (go ahead). I Use the RAD tool DELPHI 6.0. Will Firebird service native Drivers to Firebird or only by ODBC. How locks the future to service the RAD tools DELPHI and C++ Builder and Kylix. I think this are question that is very important for me and i think for many other people to. 12 Mar dbExpress InterBase 6.5 driver for Delphi 6 available The Delphi 6 registered users site now has the dbExpress driver for InterBase 6.5 12 Mar Additional dbExpress driver options John K culled a list of third-party drivers available for dbExpress from the dbExpress newsgroups, and has compiled it in this article. |
|
From: Chris M. <ch...@ev...> - 2002-03-08 18:55:05
|
I am using this driver in an ASP page running on Windows 2000 SP 2 IIS 5. If I try to read from a recordset with a timestamp that has an ODD hour (e.g 3:00, 5:00, etc) it will error out. Easysoft driver works under identical circumstances. As far as I can tell this only blows up with an odd hour. |
|
From: Kevin S. <kev...@at...> - 2002-03-08 04:24:42
|
Paul -- I reinstalled a demo version of Crystal the other day to play with
the RDC and the installation trashed the changes I had made to the registry.
I didn't notice until your post and found that I was getting the same {oj
problem you described (and that I was having last week). I "re-registered"
the odbcjdbc.dll and everything is now working fine.
Maybe this happened to you too?
Kevin
""Paul Schmidt"" <pa...@tr...> wrote in message
news:3C85C47E.9834.3B86B@localhost...
> NG:
>
> Okay, the Purolator guy just left, and I now have Crystal V8.5 (oh joy, oh
bliss) gee,
> it's a heck of a lot bigger, I think the manual has grown too....
>
> A Quick install, grab a report, and what do you mean invalid token on line
1
> character 345, okay so it's an oj ( ......
>
> funny thing is the Gemini driver creates SQL without the (, I use a
version patched
> thanks to Dmitri, however this is an interesting problem....
>
> That's bad enough, however there is a second problem, if I create a new
report, it
> doesn't use the ( but it then complains that the first table name is an
invalid token....
>
> Anyone have any ideas?
>
> Paul Paul Schmidt
> Tricat Technologies
> pa...@tr...
> www.tricattechnologies.com
>
>
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>
|
|
From: Dmitry Y. <di...@us...> - 2002-03-06 13:42:44
|
Hi Paul, > Okay, the Purolator guy just left, and I now have Crystal > V8.5 (oh joy, oh bliss) gee, > it's a heck of a lot bigger, I think the manual has grown too.... > > A Quick install, grab a report, and what do you mean invalid > token on line 1 > character 345, okay so it's an oj ( ...... > > funny thing is the Gemini driver creates SQL without the (, I > use a version patched > thanks to Dmitri, however this is an interesting problem.... Hmmm, weird enough. Don't know what to say. > That's bad enough, however there is a second problem, if I > create a new report, it > doesn't use the ( but it then complains that the first table > name is an invalid token.... I use v8.0 but never saw such an error. Are you really really sure you've applied a patch properly? Perhaps Kevin Smith has something useful to say about v8.5. Dmitry |
|
From: Paul S. <pa...@tr...> - 2002-03-06 12:19:57
|
NG: Okay, the Purolator guy just left, and I now have Crystal V8.5 (oh joy, oh bliss) gee, it's a heck of a lot bigger, I think the manual has grown too.... A Quick install, grab a report, and what do you mean invalid token on line 1 character 345, okay so it's an oj ( ...... funny thing is the Gemini driver creates SQL without the (, I use a version patched thanks to Dmitri, however this is an interesting problem.... That's bad enough, however there is a second problem, if I create a new report, it doesn't use the ( but it then complains that the first table name is an invalid token.... Anyone have any ideas? Paul Paul Schmidt Tricat Technologies pa...@tr... www.tricattechnologies.com |
|
From: Takahiro K. <Tak...@so...> - 2002-03-04 02:36:29
|
Hello,
Now I am trying to open InterBase DB by IIS-ASP(ADO) with recent IBPhoenix
Open Source ODBC Driver on Windows2000, but I have not done it.
When I try it, I am told 'unavailable database' from 'Microsoft OLE DB
Provider for ODBC Drivers'.
ASP-Script is as follows:
<% Set CON = Server.CreateObject("ADODB.Connection") %>
<% CON.Open("DSN") %>
<% CON.Close %>
If anyone knows the reason or how to solve the problem, please let me know.
Takahiro Konno
Tak...@so...
4.Mar.2002
|
|
From: Paul R. <pr...@ib...> - 2002-03-01 07:45:03
|
Paul Schmidt wrote: > > > I got the following error building the driver > > Linking... > .\OdbcJdbcSetup.def : warning LNK4104: export of symbol > "DllRegisterServer" should be PRIVATE > Creating library ../Release/OdbcJdbcSetup.lib and object > ../Release/OdbcJdbcSetup.exp > LINK : warning LNK4089: all references to "SHELL32.dll" discarded > by /OPT:REF > > Does anyone know what needs to be altered to get rid of this error? > These are warnings - not errors. Unless you have set the compiler to treat errors as warnings you will now have a working driver. Paul -- Paul Reeves http://www.ibphoenix.com taking InterBase further |
|
From: Paul S. <pa...@tr...> - 2002-02-28 22:04:44
|
Dear list: I got the following error building the driver Linking... .\OdbcJdbcSetup.def : warning LNK4104: export of symbol "DllRegisterServer" should be PRIVATE Creating library ../Release/OdbcJdbcSetup.lib and object ../Release/OdbcJdbcSetup.exp LINK : warning LNK4089: all references to "SHELL32.dll" discarded by /OPT:REF Does anyone know what needs to be altered to get rid of this error? Thanks Paul Schmidt Tricat Technologies pa...@tr... www.tricattechnologies.com |
|
From: Dmitry Y. <di...@us...> - 2002-02-20 08:24:10
|
Hi Kevin, > Most importantly -- it works! Glad to hear it. A long while ago I had the same problem and this patch helped me too. > Being a novice with SQL, I still don't understand why the SQL > is created > using "alias names" (my term, probably very wrong) to the two tables > (PATIENT1 instead of PATIENT and PROVIDER1 instead of > PROVIDER). It would > seem more direct to simply reference the actual table names. > What am I missing? Crystal allows you to have a number of instances of any table in your report. In this case aliases are the only way to avoid an ambiguity and Crystal requires you to provide them for tables that are used more than once. But internally Crystal doesn't care how many times every table appears in your report and generate SQL aliases for all cases, even when you have only one table. I agree it's stupid, but it's how it works. > Thanks for your help! You're welcome. Cheers, Dmitry |
|
From: Kevin S. <kev...@at...> - 2002-02-20 00:37:12
|
Thanks Dimitry!
I ran outjoin.reg (from your link) to create the Outerjoin folder in the
registry at
Hkey_Current_User / Software / Seagate Software / Crystal Reports /
DatabaseOptions / Outerjoin
Then I added the "odbcjdbc" driver name to the "PlusEqual" section within
"Outerjoin" and Crystal now generates much different SQL (below):
SELECT
PATIENT1."NAMEFIRST", PATIENT1."NAMELAST",
PATIENT1."PATIENTID", PATIENT1."PROVIDERID",
PROVIDER1."NAMEFIRST", PROVIDER1."NAMELAST"
FROM
"PATIENT" PATIENT1,
"PROVIDER" PROVIDER1
WHERE
PATIENT1."PROVIDERID" = PROVIDER1."PROVIDERID" AND
PATIENT1."PATIENTID" < 2000
ORDER BY
PATIENT1."PROVIDERID" ASC
Most importantly -- it works!
Being a novice with SQL, I still don't understand why the SQL is created
using "alias names" (my term, probably very wrong) to the two tables
(PATIENT1 instead of PATIENT and PROVIDER1 instead of PROVIDER). It would
seem more direct to simply reference the actual table names. What am I
missing?
Thanks for your help!
Kevin.
Previous code included below for reference:
SELECT
PATIENT1."NAMEFIRST", PATIENT1."NAMELAST",
PATIENT1."PATIENTID", PATIENT1."PROVIDERID",
PROVIDER1."NAMENAMEFIRST", PROVIDER1."NAMELAST"
FROM
{ oj "PATIENT" PATIENT1 INNER JOIN "PROVIDER" PROVIDER1 ON
PATIENT1."PROVIDERID" = PROVIDER1."PROVIDERID"}
WHERE
PATIENT1."PATIENTID" < 2000
ORDER BY
PATIENT1."PROVIDERID" ASC
|
|
From: Kevin S. <ke...@af...> - 2002-02-19 18:27:38
|
Sorry Ann,
Dynamic SQL Error
SQL error code = -104
Token unknown - line 6, char 8
"PATIENT"
I don't know what I was thinking...the query works in IBConsole if I delete
the opening '{oj' and the closing '}'
Crystal Reports 8.5 won't let me edit the SELECT portion of the SQL below.
SELECT
PATIENT1."HOMEPHONE", PATIENT1."MOBILEPHONE",
PATIENT1."NAMEFIRST", PATIENT1."NAMELAST", PATIENT1."PATIENTID",
PATIENT1."PROVIDERID", PATIENT1."WORKPHONE",PROVIDER1."NAME"
FROM
{ oj "PATIENT" PATIENT1 INNER JOIN "PROVIDER" PROVIDER1 ON
PATIENT1."PROVIDERID" = PROVIDER1."PROVIDERID"}
It appears the ODBC driver doesn't like the '{oj' syntax. Both EasySoft and
Gemini ODBC process the query correctly.
For the heck of it, I deleted the {oj...} within Crystal and the query
seems to execute properly. I'll double-check the result set and let you
know if it causes a problem.
I generated a new report similar to the previous, but specifying the Gemini
ODBC datasource and Crystal generated slightly different SQL:
SELECT
PATIENT.PATIENTID, PATIENT.NAMELAST, PATIENT.NAMEFIRST,
PATIENT.HOMEPHONE,
PROVIDER.PROVIDERID, PROVIDER.NAME
FROM
{ oj PATIENT PATIENT INNER JOIN PROVIDER PROVIDER ON
PATIENT.PROVIDERID = PROVIDER.PROVIDERID}
WHERE
PATIENT.PATIENTID < 2000
ORDER BY
PROVIDER.PROVIDERID ASC,
PATIENT.NAMELAST ASC
This executed properly as is, and also worked when I deleted the {oj...}
Thanks,
Kevin
-----Original Message-----
From: Ann W. Harrison [mailto:aha...@ib...]
Sent: Tuesday, February 19, 2002 10:30 PM
To: ke...@af...;
fir...@li...
Subject: Re: [Firebird-odbc-devel] Crystal Reports 8.5
At 04:36 PM 2/18/2002 -0700, Kevin Smith wrote:
>One more thing. The statement fails when executed within IB Console as
>well.
"Fails?" Returns no rows? Returns an error message? Crashes the
IBServer process? Crashes the server system? Sets the lab on fire?
Ann
|
|
From: Ann W. H. <aha...@ib...> - 2002-02-19 15:33:58
|
At 04:36 PM 2/18/2002 -0700, Kevin Smith wrote: >One more thing. The statement fails when executed within IB Console as >well. "Fails?" Returns no rows? Returns an error message? Crashes the IBServer process? Crashes the server system? Sets the lab on fire? Ann |
|
From: Dmitry Y. <di...@us...> - 2002-02-19 12:19:07
|
Hi Kevin,
> One more thing. The statement fails when executed within IB
> Console as
> well.
I believe the issue you described in your posts is easy to solve. The {oj
...} syntax you mentioned is internal Crystal's format for joins and it is
later replaced with the native join syntax of the data source. But it
doesn't work well with InterBase/Firebird and this driver. There was a patch
for this case somewhere on Seagate tech support site and some time ago I've
uploaded it to the file section of ib-support, so you can get it at:
http://groups.yahoo.com/group/ib-support/files/odbcregs.zip
Take a look at the readme and correct a couple of lines in the registry.
Hope this helps.
> Is there an easier way for me to post? I copied from
> the archive and sent email to
> fir...@li....
Get your account on the sourceforge site and subscribe to this list. Sorry,
don't remember exact URL to join the list at the moment.
Cheers,
Dmitry
|
|
From: Kevin S. <kev...@at...> - 2002-02-19 03:02:33
|
Paul, Dimitry -- thanks for the post. I'm getting back to using Firebird
.9.4 with a Delphi 6 application for the first time in many years (1992).
The VisualLinkingExpert in Crystal 8.5 creates the following code to create
a join between two tables:
SELECT
PATIENT1."HOMEPHONE", PATIENT1."MOBILEPHONE", PATIENT1."NAMEFIRST",
PATIENT1."NAMELAST", PATIENT1."PATIENTID", PATIENT1."PROVIDERID",
PATIENT1."WORKPHONE",
PROVIDER1."NAME"
FROM
{ oj "PATIENT" PATIENT1 INNER JOIN "PROVIDER" PROVIDER1 ON
PATIENT1."PROVIDERID" = PROVIDER1."PROVIDERID"}
WHERE
PATIENT1."PATIENTID" < 2000
ORDER BY
PATIENT1."PROVIDERID" ASC,
PATIENT1."NAMELAST" ASC
and it fails. If I use the Easysoft ODBC this SQL works ... I can't even
connect using the Intersolv ODBC driver. The name of the "left" table is
PATIENT and the name of the "right" table is PROVIDER, linking fields of
type Integer (primary key for PROVIDER). It is my understanding that
Crystal won't allow me to change the SELECT clause. I've selected DIALECT 3,
for no reason other than it seemed newer-cooler than DIALECT 1. Maybe this
is my problem.
Is there an easier way for me to post? I copied from the archive and sent
email to fir...@li....
Another, less pressing issue: Microsoft Products (Access, Excel, Word)
can't access the tables. This is a problem for me as some of my customers
want to use the MS products to analyze small datasets, do mail merges with
Word, etc.
Thanks,
Kevin
FROM: Paul SchmidtDATE: 02/18/2002 07:06:17SUBJECT: RE:
[Firebird-odbc-devel] Crystal Reports 8.5
Dmitry Yemanov Wrote on 02/15/2002 23:11:04
>Hi Kevin,
> Has anyone tried the ODBC driver with Crystal
Reports?
Dmitry:
I am trying to reply to this, having scraped the text
from the archive, hopefully the result is
understandable.
>Yep, but I wouldn't call it a successful attempt.
>After some debugging, I've
>finally found and fixed the main problem and Crystal
>(I use version 8.0)
>started to work with this driver and my databases,
>but... not exactly the
>way I expected it to work. There's one magic issue I
>still cannot figure
>out. For the time being, I've stopped all my
>investigations due to complete
>lack of time and my changes are still in my private
>source tree, but, once
>the remaining problem is solved, I'll commit the
>changes to the main CVS
>tree or upload them as a separate patch.
Could you send me your source, and let me take a look
at it, sometimes another pair of eyes can help. I
have an old version of Crystal (4 actually -- planning
to upgrade RSN), and the driver seems to work as is,
except that on a Dialect 3 database dates and times
look really wierd, unless I do really oddball stuff,
like use a view to turn a time into a string field, I
would hate to do that with dates as well, then again
Crystal 4 doesn't support time fields (kind of dumb
IMNSHO). The main CVS tree is downright ancient, I
was thinking it had actually been abandoned.
Thanks,
Paul
|
|
From: Kevin S. <kev...@at...> - 2002-02-19 01:52:54
|
Paul / Dimitry -- One more thing. The statement fails when executed within IB Console as well. Thanks. Kevin |
|
From: Dmitry Y. <di...@us...> - 2002-02-18 21:39:52
|
Hi Paul,
> Could you send me your source, and let me take a look
> at it, sometimes another pair of eyes can help. I
> have an old version of Crystal (4 actually -- planning
> to upgrade RSN), and the driver seems to work as is,
> except that on a Dialect 3 database dates and times
> look really wierd, unless I do really oddball stuff,
> like use a view to turn a time into a string field, I
> would hate to do that with dates as well, then again
> Crystal 4 doesn't support time fields (kind of dumb
> IMNSHO). The main CVS tree is downright ancient, I
> was thinking it had actually been abandoned.
Yes, the only problems I've got are with date/time fields also. All kinds of
them in both dialect 1 and 3 databases are recognized as strings by Crystal.
I believe it cannot understand what the data type really is and supposes
string by default in this situation. Aside from being simply not working,
such a supposal often causes it to die. AFAIU, the reason is obvious -
Crystal is not ODBC 3.x conformant.
Since I definitely don't want to do a lot of tricky things (like the stuff
you described), I'd very much like to fix it. This mentioned problem has
been solved by changing the internally used JDBC type mapping from
SQL_TYPE_* types to SQL_* types, thus downgrading the driver to ODBC 2.x:
diff -r1.3 IscDbc.h
76,78c76,78
< #define JDBC_DATE 91
< #define JDBC_TIME 92
< #define JDBC_TIMESTAMP 93
---
> #define JDBC_DATE 9 // was: 91
> #define JDBC_TIME 10 // was: 92
> #define JDBC_TIMESTAMP 11 // was: 93
diff -r1.1.1.1 Sqlda.cpp
382c382
< return TIME;
---
> return JDBC_TIME;
385c385
< return jdbcDATE;
---
> return JDBC_DATE;
After that, Crystal has started to recognize all date/time fields in any
dialect properly and the problem seemed to be gone. But then I've
encountered an interesting effect while was trying to use those fields in
the selection formula. It's easy to reproduce. Let's say I have MY_TABLE
table with only one MY_MONTH field, declared as DATE (you may use either
dialect 1 or 3). This table has 24 rows, one per month, with field values
from 01-JAN-2001 to 01-DEC-2002.
Now, with the following formula:
{MY_TABLE.MY_MONTH} >= date('01.01.2002')
I see the expected 12 rows, but just after a very minor change:
{MY_TABLE.MY_MONTH} < date('01.01.2002')
I see nothing. The first fetch returns EOF. Where is the another half of my
data? So it seems to be either Crystal's or driver's problem. Note also
that:
a) the same query succeeds when Crystal is connected through the Oracle ODBC
driver
b) the same query succeeds with this driver when I override selection
formula with direct SQL and use a date literal, or when I use it as a
constant query (without parameters) and run it from any other application
AFAIK, any time a constant is used in the selection formula, Crystal uses
parametrized query (for ODBC data sources), so it may be a part of the
problem. Unfortunately, I don't have any program that allows query execution
via ODBC and always uses parameter binding. All my debug attempts were
unsuccessful - both statements are passed and prepared correctly, in both
cases parameters has the same value. Since I don't believe that I've found
another bug in the engine ;-), I prefer to consider it a driver problem that
I just cannot figure out.
Could you test my example and let me know the results? Maybe I have a
poltergeist in my computer...
Cheers,
Dmitry
|
|
From: Paul S. <pa...@tr...> - 2002-02-18 15:00:52
|
Dmitry Yemanov Wrote on 02/15/2002 23:11:04 >Hi Kevin, >> Has anyone tried the ODBC driver with Crystal Reports? Dmitry: I am trying to reply to this, having scraped the text from the archive, hopefully the result is understandable. >Yep, but I wouldn't call it a successful attempt. >After some debugging, I've >finally found and fixed the main problem and Crystal >(I use version 8.0) >started to work with this driver and my databases, >but... not exactly the >way I expected it to work. There's one magic issue I >still cannot figure >out. For the time being, I've stopped all my >investigations due to complete >lack of time and my changes are still in my private >source tree, but, once >the remaining problem is solved, I'll commit the >changes to the main CVS >tree or upload them as a separate patch. Could you send me your source, and let me take a look at it, sometimes another pair of eyes can help. I have an old version of Crystal (4 actually -- planning to upgrade RSN), and the driver seems to work as is, except that on a Dialect 3 database dates and times look really wierd, unless I do really oddball stuff, like use a view to turn a time into a string field, I would hate to do that with dates as well, then again Crystal 4 doesn't support time fields (kind of dumb IMNSHO). The main CVS tree is downright ancient, I was thinking it had actually been abandoned. Thanks, Paul >Anyway, could you provide more information about your >problems (if you have them)? Paul Schmidt Tricat Technologies pa...@tr... www.tricattechnologies.com |
|
From: Dmitry Y. <di...@us...> - 2002-02-16 07:15:48
|
Hi Kevin, > Has anyone tried the ODBC driver with Crystal Reports? Yep, but I wouldn't call it a successful attempt. After some debugging, I've finally found and fixed the main problem and Crystal (I use version 8.0) started to work with this driver and my databases, but... not exactly the way I expected it to work. There's one magic issue I still cannot figure out. For the time being, I've stopped all my investigations due to complete lack of time and my changes are still in my private source tree, but, once the remaining problem is solved, I'll commit the changes to the main CVS tree or upload them as a separate patch. Anyway, could you provide more information about your problems (if you have them)? Cheers, Dmitry |
|
From: Kevin S. <kev...@at...> - 2002-02-15 21:10:20
|
Has anyone tried the ODBC driver with Crystal Reports? |
|
From: Canou <chr...@wa...> - 2002-02-06 12:20:19
|
Sorry for my English. I would like to create Setup for my program. This one is useful of data bases of the Interbase type. On the level of the application in itself, I do not have a problem to put my files in my Setup. The problem that I meet, it is that I would like that my apllication can turn on a ordi without it being Delphi Installé there (or rather the basic engine of data of Interbase). It is necessary thus that I make install the basic engine of data of IB when the user launches Setup. I have already to create Setup, but this last installed the BDE, but apparently, that does not go. Can somebody make Setup with the basic engine of data of IB at " the interior "? Moreover, I made some search on top and I saw that one had the compocants of Delphi: IBInstall... For what is used it? Thank you for all answers. |
|
From: Hussain, S. (UK - Epsom) <shu...@bw...> - 2002-02-05 17:48:38
|
Can you use the ODBC driver to return BLOB fields. My SQL statement is: SELECT Documentation FROM ADOBJECT; where Documentation is a BLOB field. I am using the latest ODBC driver and using it in ADO 2.1 with VB6 SP5. If I ask for any other field in the ADOBJECT table the SQL returns a recordset with no problems. However requesting the Documentation fields causes a fatal exception and crashes the whole VB environment!! I assume the fact that it is a BLOB field is the probem. Is this supported? Any comments/help would be appreciated. Regards Marc fakkel ____________________________________ Saiyid T.E. Hussain B&W Deloitte Tel: +44 1372 824000 Horizon House Direct Dial: +44 1372 824180* 28 Upper Street Fax: +44 1372 802824 * Epsom, Surrey <mailto:shu...@bw...> * KT17 4RS www.bw-deloite.com IMPORTANT NOTICE This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it (with the title "received in error") to the sender then delete the email and destroy any copies of it. We would be grateful if you would also copy the communication to IT....@de... This communication is from Deloitte & Touche whose principal office is at Stonecutter Court, 1 Stonecutter Street, London, EC4A 4TR, United Kingdom. A list of partners' names is available at this address. Deloitte & Touche is authorised by the Financial Services Authority in respect of regulated activities. |
71 messages has been excluded from this view by a project administrator.
