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: Paul R. <pr...@ib...> - 2002-06-26 06:05:49
|
Roger Gammans wrote: > > Well, I unpacked to tar file from the iibpheonix website orignally, > but then I 'cvs update'd it (By editting all the CVS/Root files) > hopefully back to the head. Editing all the CVS/Root files? That seems like a technique the Cedarqvist manual overlooked. > Except I've never used the m$ build toolkit[0] , all my windows stuff > is built under mingw. I can only see those files in the > OdbcJdbcSetup directory, which is presuambly just for the installer. > Try doing a fresh CVS checkout. Then, from MSVC, open the workspace in the root (ie OdbcJdbc) directory. After that everything should be fairly straightforward. The project dependancies are set up so that you just build OdbcJdbcSetup. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Roger G. <ro...@co...> - 2002-06-25 18:18:19
|
Hi Apoolgies forgot to attach the patch that solves the SQLGetInfo and SQLBindXXX problems. Here it is. TTFN -- Roger. Master of Peng Shui. (Ancient oriental art of Penguin Arranging) |
From: <car...@ho...> - 2002-06-25 16:50:45
|
Hello: 1. I´m testing the last CVS sources under Visual Foxpro and the driver crashes when V.Foxpro made a call to SQLPrepare and a call to SQLNumResultcols ( almost to me in my test ), the problem is in this block of code: if (!resultSet ){ // Contributed by B. Schulte // if the resultSet does not exist, execute it, to get a valid resultSet // Foxpro calls this function to get all column-descriptions for its // remote-views. // This fixes the bug : ' I can't edit my remote-views in Visial FoxPro' this->executeStatement(); } I solve the problem of the views in Visual foxpro in other way, i put here my code for solve it : OdbcStatement.h: Add this at line 153: bool updatePreparedResultSet; OdbcStatement.cpp: Add this line 112 ( OdbcStatement::OdbcStatement ): updatePreparedResultSet = true; Add this line 242 ( OdbcStatement::sqlPrepare ): if( updatePreparedResultSet ) setResultSet(statement->getResultSet()); Add this line 929 ( OdbcStatement::sqlExecute ): if ( resultSet ) releaseResultSet(); Add this line 844 ( OdbcStatement::sqlExecuteDirect ): updatePreparedResultSet = false; int retcode = sqlPrepare (sql, sqlLength); updatePreparedResultSet = true; 2. With last CVS Sources parametrized statements don´t work ( Tested in Visual Foxpro ). The problem seems to be in the new way for exec the statements ( the changes for DATA_AT_EXEC parameters ) because i have my own code for DATA_AT_EXEC parameters ( that is unfinished work ) in other tree source for the driver and it works well with the rest of changes of the last CVS sources ( O dont test Blob fields ). Best regards Carlos Guzmán Álvarez |
From: Paul R. <pr...@ib...> - 2002-06-25 14:22:38
|
Roger Gammans wrote: > Hi > > > For problems 1 + 2) I have attached an experimental patch > which weems to solve the problems here under linux, I'm the maintainer of the driver. You can submit the patches to me privately, or post them here. There are a few developers working on the code that may be interested. > are there some intructions for compileing the code for > Windows (which compiler to use etc,?), so I can see if > the patch works there? > Have you actually pulled the source out of CVS? The presence of the .DSW and .DSP files give the game away a bit. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Paul R. <pr...@ib...> - 2002-06-25 14:18:22
|
CarlosGuzm=E1n =C1lvarez wrote: > Hello: >=20 > Im trying to make a connection with the driver in Visual Studio .Net=20 > Beta 2 ( Spanish ), but it don't connect, the problem is > that the connection throguth OleDB for ODBC provider get info about the= =20 > server name and this is unsuportted by the driver, i made the next=20 > changes to solve this: >=20 Thanks for this. It all seems uncontroversial and I've committed it 'as=20 is', apart from changing 'InterBase' to 'Firebird / InterBase(r)'. Paul --=20 Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: <car...@ho...> - 2002-06-25 11:34:55
|
Hello: I´m trying to make a connection with the driver in Visual Studio .Net Beta 2 ( Spanish ), but it don't connect, the problem is that the connection throguth OleDB for ODBC provider get info about the server name and this is unsuportted by the driver, i made the next changes to solve this: InfoItems.h ( Line 79 ) Change: UITEM (SQL_SERVER_NAME, 0) For : CITEM (SQL_SERVER_NAME, 0) OdbcConnection.cpp Add this at line 572 ( OdbcConnection::sqlGetInfo ): case SQL_SERVER_NAME: string = metaData->getDatabaseServerName(); break; Connection.h Add this at line 120 ( into the definition of theclass DatabaseMetaData ): virtual const char* getDatabaseServerName() = 0; IscDatabaseMetadata.h Add this at line 64: virtual const char* getDatabaseServerName(); IscDatabaseMetadata.cpp Add this at line 254: const char* IscDatabaseMetaData::getDatabaseServerName() { return "InterBase Server"; } Best regards Carlos Guzmán Álvarez |
From: Roger G. <ro...@co...> - 2002-06-25 11:19:17
|
Hi I've been using Firebird and the ibphoenix ObdcJdbc driver from the website for the last week on so here, with iODBC 3.0.6 and wxWindows but have been having some trouble. 1) SQLGetInfo seems to return SUCCESS_WITH_INFO if the previous cal failed with SQLError. 2) SQLBindXX calls fail in during new, apparently trying to allocate obscene amounts of memory. 3) If Prepare/Execute/ExecDirect fail, the SQLError call never seems to leave libiODBC and then core dumps. Has any seen 3) before? it looks like and iODBC bug but I haven't had a chance to trace it throughly, but certainly I haven't had the bug before with other drivers (Informix comes to mind). For problems 1 + 2) I have attached an experimental patch which weems to solve the problems here under linux, are there some intructions for compileing the code for Windows (which compiler to use etc,?), so I can see if the patch works there? TTFN -- Roger. Master of Peng Shui. (Ancient oriental art of Penguin Arranging) |
From: Andrea C. P. <ac...@bi...> - 2002-06-24 07:40:10
|
Hi, probably it is a ODBC driver problem. I tried it with GEMINI and VFP6 and works fine. -- Andrea Chiado Piat Bit Informatica s.r.l. Progettazione e Sviluppo ""B. Schulte"" <sc...@de...> ha scritto nel messaggio news:3D136E4A.20165.28BCF0@localhost... > Hi, > > I'm sorry, but I can't reproduce this behaviour. > By the way: the are is real DECIMAL-type in FireBird. It is internally > converted to NUMERIC or DOUBLE (and also shown as this). > maybe you can tell me step by step what you did. > I remember that I saw this kind of error also with the 5.6-odbc-driver, > that came with the first release for Interbase 6.0. > Maybe this is a FoxPro-specific problem (maybe not definitively) > > B. Schulte > > > > > > > Hello: > > > > > > In visual foxpro when you execute a Statement with sqlexec like this: > > sqlexec( gnHConn,"SELECT SUM(field) FROM TABLE", "CURSOR") > > if the field in the sum is a DECIMAL field in Firebird, Visual Foxpro > > converts it in Character because the driver returns JDBC_BIGINT as > > column type i have a little fix for this issue and return JDBC_DECIMAL > > instead of SQL_BIGINT for DECIMAL FIELDS( i 4m very pleased if any can > > confirm to me that this fix is correct ): > > > > > > Sqlda.h: > > > > Change: > > static int getSqlType (int iscType, int subType); > > static const char* getSqlTypeName (int iscType, int subType); > > to : > > > > static int getSqlType (int iscType, int subType, int sqlScale); > > static const char* getSqlTypeName (int iscType, int subType, int > > sqlScale); > > > > > > > > ------------------------------------------------------- > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > Firebird-odbc-devel mailing list > Fir...@li... > https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel > |
From: Paul R. <pr...@ib...> - 2002-06-24 06:58:35
|
William L. Thomson Jr. wrote: > I was looking at the InterBase examples that come with IB 6.0, but they > all seem to use isc_attach. Which I assume is for db residing on the > same machine. Where my db will be on a remote machine. isc_attach() is the only way to attach to a database. The client library will parse the database name and call the relevant server. You need this format: servername:/path/to/my/database.gdb > If this is the wrong list, if you could please tell me what list to use > instead. > None of the Firebird lists are for general support - they all concentrate on supporting internal development of the engine, or drivers etc. The ib-support list, hosted on yahoo, is a good all-round support list for InterBase and Firebird questions. See http://firebird.sourceforge.net/index.php?op=lists for more info. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: William L. T. Jr. <su...@ob...> - 2002-06-24 00:42:54
|
Sorry if this is the wrong mailing list. I would like to connect to InterBase/Firebird remotely from Linux using C or C++. I am not sure if ODBC drivers are made for, or can be used in Linux. I have been familiar with ODBC drivers on Windows platforms, but I am not in a MS env, pure Linux. I have a dedicated DB server that I need to connect to from other machines on the network. Pretty much lan only, maybe internet at a later date. I have been using the JDBC driver, InterClient 2.0 for about a year now and it's great. However I am creating some apps in C/C++ not Java, so I need to figure out how to connect to InterBase/Firebird using C/C++. I was looking at the InterBase examples that come with IB 6.0, but they all seem to use isc_attach. Which I assume is for db residing on the same machine. Where my db will be on a remote machine. Not sure if their are differences in the way you connect to IB or Firebird. At the moment I am running IB 6.0, but would like to eventually switch over Firebird. So if there are differences I would like to be aware of them before I get to deep into writing my app. If this is the wrong list, if you could please tell me what list to use instead. Thank you. -- Sincerely, William L. Thomson Jr. Support Group Obsidian-Studios Inc. 439 Amber Way Petaluma, Ca. 94952 Phone 707.766.9509 Fax 707.766.8989 http://www.obsidian-studios.com |
From: Carlos G.A. <car...@ho...> - 2002-06-21 16:55:14
|
Hello: If you have in Interbase/Firebird a table like this: create table DECIMAL_TEST( codigo char(3), importe decimal( 18,5 ) ); And you make this in visual foxpro: local lnHConn lnHConn = sqlconnect( "nombre_conexion" ) sqlexec( lnHConn, "select sum(importe) from DECIMAL_TEST", "TEST" ) The cursor "TEST" have a field character(20) because Visual Foxpro converts SQL_BIGINT ( the datatype returned for the driver for the field when it have to return SQL_DECIMAL ) to character, my fix solve this and with it the field is numeric. Best Regards Carlos Guzmán Álvarez >From: "B. Schulte" <sc...@de...> >To: fir...@li... >Subject: [Firebird-odbc-devel] RE: DECIMAL fields AND Visual Foxpro >Date: Fri, 21 Jun 2002 18:19:54 +0200 > >Hi, > >I'm sorry, but I can't reproduce this behaviour. >By the way: the are is real DECIMAL-type in FireBird. It is internally >converted to NUMERIC or DOUBLE (and also shown as this). >maybe you can tell me step by step what you did. >I remember that I saw this kind of error also with the 5.6-odbc-driver, >that came with the first release for Interbase 6.0. >Maybe this is a FoxPro-specific problem (maybe not definitively) > > B. Schulte > > > > > > > Hello: > > > > > > In visual foxpro when you execute a Statement with sqlexec like this: > > sqlexec( gnHConn,"SELECT SUM(field) FROM TABLE", "CURSOR") > > if the field in the sum is a DECIMAL field in Firebird, Visual Foxpro > > converts it in Character because the driver returns JDBC_BIGINT as > > column type i have a little fix for this issue and return JDBC_DECIMAL > > instead of SQL_BIGINT for DECIMAL FIELDS( i ´m very pleased if any can > > confirm to me that this fix is correct ): > > > > > > Sqlda.h: > > > > Change: > > static int getSqlType (int iscType, int subType); > > static const char* getSqlTypeName (int iscType, int subType); > > to : > > > > static int getSqlType (int iscType, int subType, int sqlScale); > > static const char* getSqlTypeName (int iscType, int subType, int > > sqlScale); > > > > > > > >------------------------------------------------------- >Sponsored by: >ThinkGeek at http://www.ThinkGeek.com/ >_______________________________________________ >Firebird-odbc-devel mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel _________________________________________________________________ MSN Photos es la manera más sencilla de compartir e imprimir sus fotos: http://photos.msn.com/support/worldwide.aspx |
From: B. S. <sc...@de...> - 2002-06-21 16:19:27
|
Hi, I'm sorry, but I can't reproduce this behaviour. By the way: the are is real DECIMAL-type in FireBird. It is internally converted to NUMERIC or DOUBLE (and also shown as this). maybe you can tell me step by step what you did. I remember that I saw this kind of error also with the 5.6-odbc-driver, that came with the first release for Interbase 6.0. Maybe this is a FoxPro-specific problem (maybe not definitively) B. Schulte > > Hello: > > > In visual foxpro when you execute a Statement with sqlexec like this: > sqlexec( gnHConn,"SELECT SUM(field) FROM TABLE", "CURSOR") > if the field in the sum is a DECIMAL field in Firebird, Visual Foxpro > converts it in Character because the driver returns JDBC_BIGINT as > column type i have a little fix for this issue and return JDBC_DECIMAL > instead of SQL_BIGINT for DECIMAL FIELDS( i ´m very pleased if any can > confirm to me that this fix is correct ): > > > Sqlda.h: > > Change: > static int getSqlType (int iscType, int subType); > static const char* getSqlTypeName (int iscType, int subType); > to : > > static int getSqlType (int iscType, int subType, int sqlScale); > static const char* getSqlTypeName (int iscType, int subType, int > sqlScale); > > |
From: Carlos G.A. <car...@ho...> - 2002-06-19 17:40:36
|
Hello: In visual foxpro when you execute a Statement with sqlexec like this: sqlexec( gnHConn,"SELECT SUM(field) FROM TABLE", "CURSOR") if the field in the sum is a DECIMAL field in Firebird, Visual Foxpro converts it in Character because the driver returns JDBC_BIGINT as column type i have a little fix for this issue and return JDBC_DECIMAL instead of SQL_BIGINT for DECIMAL FIELDS( i ´m very pleased if any can confirm to me that this fix is correct ): Sqlda.h: Change: static int getSqlType (int iscType, int subType); static const char* getSqlTypeName (int iscType, int subType); to : static int getSqlType (int iscType, int subType, int sqlScale); static const char* getSqlTypeName (int iscType, int subType, int sqlScale); Sqlda.cpp: int Sqlda::getColumnType(int index) { XSQLVAR *var = sqlda->sqlvar + index - 1; return getSqlType (var->sqltype, var->sqlsubtype, var->sqlscale); } int Sqlda::getSqlType(int iscType, int subType, int sqlScale) { switch (iscType & ~1) { case SQL_TEXT: return JDBC_CHAR; case SQL_VARYING: return JDBC_VARCHAR; case SQL_SHORT: if ( sqlScale < 0 ) return JDBC_DECIMAL; return JDBC_SMALLINT; case SQL_LONG: if ( sqlScale < 0 ) return JDBC_DECIMAL; return JDBC_INTEGER; case SQL_INT64: if ( sqlScale < 0 ) return JDBC_DECIMAL; return JDBC_BIGINT; case SQL_QUAD: return JDBC_BIGINT; case SQL_FLOAT: return JDBC_REAL; case SQL_DOUBLE: if ( sqlScale < 0 ) return JDBC_DECIMAL; return JDBC_DOUBLE; case SQL_TIMESTAMP: return JDBC_TIMESTAMP; case SQL_TYPE_TIME: return TIME; case SQL_TYPE_DATE: return jdbcDATE; case SQL_BLOB: if (subType == 1) return JDBC_LONGVARCHAR; return JDBC_LONGVARBINARY; case SQL_ARRAY: NOT_SUPPORTED("array", 0, "", 0, ""); } return 0; } const char* Sqlda::getSqlTypeName(int iscType, int subType, int sqlScale) { switch (iscType & ~1) { case SQL_TEXT: return "CHAR"; case SQL_VARYING: return "VARCHAR"; case SQL_SHORT: if ( sqlScale < 0 ) return "DECIMAL"; return "SMALLINT"; case SQL_LONG: if ( sqlScale < 0 ) return "DECIMAL"; return "INTEGER"; case SQL_INT64: if ( sqlScale < 0 ) return "DECIMAL"; return "BIGINT"; case SQL_FLOAT: return "REAL"; case SQL_DOUBLE: if ( sqlScale < 0 ) return "DECIMAL"; return "DOUBLE PRECISION"; case SQL_QUAD: return "BIGINT"; case SQL_BLOB: if (subType == 1) return "LONG VARCHAR"; return "LONG VARBINARY"; case SQL_TIMESTAMP: return "TIMESTAMP"; case SQL_TYPE_TIME: return "TIME"; case SQL_TYPE_DATE: return "DATE"; case SQL_ARRAY: return "ARRAY"; default: NOT_YET_IMPLEMENTED; } return "*unknown type*"; } Best regards Carlos Guzmán Álvarez _________________________________________________________________ Envíe y reciba su correo de Hotmail desde el móvil: http://mobile.msn.com |
From: <car...@ho...> - 2002-06-15 22:43:35
|
Hello: I´m testing the last cvs sources and i have ( under Visual Foxpro ) problems with SQL statements that have string parameters ( the results of the execution are incorrect ) that are not null terminated strings, i have this solution for this problem: OdbcStatement.cpp: void OdbcStatement::setParameter(Binding * binding, int parameter) { clearErrors(); if (binding && binding->indicatorPointer && *(binding->indicatorPointer) == SQL_NULL_DATA) { statement->setNull(parameter, 0); return; } try { switch (binding->cType) { case SQL_C_CHAR: { switch( *binding->indicatorPointer ) { case SQL_NTS: statement->setString (parameter, (char*) binding->pointer ); break; default: statement->setString (parameter, (char*)binding->pointer, *binding->indicatorPointer ); break; } } break; ................. } Connection.h: #define PREPAREDSTATEMENT_VERSION 1 class PreparedStatement : public Statement { public: ......... virtual void setString(int index, const char * string, int length) = 0; ......... } IscCallableStatement.h: class IscCallableStatement : public IscPreparedStatement, public CallableStatement { public: ............ virtual void setString(int index, const char * string, int length); ............ } IscCallableStatement.cpp: void IscCallableStatement::setString(int index, const char * string, int length) { Parent::setString(index, string, length); } IscPreparedStatement.h: class IscPreparedStatement : public IscStatement, public PreparedStatement { public: ......... virtual void setString(int index, const char * string, int length); ......... } IscPreparedStatement.cpp: void IscPreparedStatement::setString(int index, const char * string, int length) { getParameter (index - 1)->setString (length, string, true); } Best Regards Carlos Guzmán Álvarez |
From: Andre P. <an...@de...> - 2002-06-13 13:12:31
|
Bde reads wrong values of numeric or decimal field (ex: Numeric(15,2) = with value =3D 0.8 is readed like 80) when i use OBDC Firebird. I thing = the problem is with de scale of the field, bde shows -2.=20 I looked at ODBC firebir's sources and i found 2 selects: the first=20 in IscColumnsResultSet.cpp "rdb$field_scale as decimal_digits" and=20 the second in IscSpecialColumnsResultSet.cpp "(f.rdb$field_scale * - 1) as decimal_digits". Is the bug in the first select?=20 I don't have C++ compiler and don't know nothing about C++. Can=20 anybody compile and send me? Thanks Andre |
From: Xpertdoc <xpe...@af...> - 2002-06-12 00:02:22
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>Untitled</title> </head> <body style="FONT-FAMILY: arial,sans-serif" bgcolor="#ffffff" bottommargin="0" leftmargin="0" marginheight="0" marginwidth="0" rightmargin="0" topmargin="0"> <table cellspacing="0" cellpadding="0" border="0" width="100%"> <tr> <td ><img src="http://www.cirai.com/communiques/xpertdoc/top.gif" width="760" height="65" alt="" border="0"></TD></TR></TABLE> <table cellspacing="0" cellpadding="0" border="0" width="760"> <TR> <TD> <div align="center" style="FONT-SIZE: 12px"><p style="COLOR: #656565">Epsilon Technologies Inc. 1200, Blvd. Chomedey Suite 105 Laval, Quebec H7V 3Z3 Canada</P></DIV></TD></TR> <tr> <td> <table cellspacing="0" cellpadding="20" border="0"> <tr> <td><h3 style="COLOR: #004999"><em>The easiest way to produce customized documents</EM></H3> <UL style="FONT-SIZE: 12px"> <LI><strong style="COLOR: #004999" >Xpertdoc Studio</STRONG> is a reporting tool that allows you to create <strong style="COLOR: #004999" >Microsoft Word</STRONG> customized documents <LI>Our template designer is fully integrated with <strong style="COLOR: #004999">Microsoft Word</STRONG> <LI><strong style="COLOR: #004999" >VBScript</STRONG> is the Language we use to define fields in the templates <LI>Our <strong style="COLOR: #004999" >ActiveX</STRONG> production engine is designed for speed and simple integration with your applications <LI>Because <strong style="COLOR: #004999" >Xpertdoc Studio</STRONG> is based on standard technology, you will not waste time learning a new designenvironment or a new programming language!</LI></UL> <h3 style="COLOR: #004999"><em>Say goodbye to your mail-merge problems!</EM></H3> <UL style="FONT-SIZE: 12px"> <LI>Combines the flexibility of word processor with the reliability of a report generator <LI>Always reliable, even when the number of document to produce is large</LI></UL> <h3 style="COLOR: #004999"><em>It is much more than just mail-merge...</EM></H3> <UL style="FONT-SIZE: 12px"> <LI>Merge any number of fields in your documents <LI>Customize the content of the documents based on conditions and loops written in VBScript</LI></UL> <h3 style="COLOR: #004999"><em>Easily access all your data...</EM></H3> <UL style="FONT-SIZE: 12px"> <LI>Databases through <strong style="COLOR: #004999">Jet Engine (DAO)</STRONG>, <strong style="COLOR: #004999" >ODBC (RDO)</STRONG> or <strong style="COLOR: #004999">OLE-DB ADO</STRONG> <LI><strong style="COLOR: #004999" >ASCII</STRONG> or <strong style="COLOR: #004999">XML</STRONG> files <LI>Any other custom data sources</LI></UL> <h3 style="COLOR: #004999"><em>Simple to integrate</EM></H3> <UL style="FONT-SIZE: 12px"> <LI>Get going with as few as six lines of code! <LI>Xpertdoc Studio can be integrated in any programming environment that supports the use of ActiveX components such as: <UL style="FONT-SIZE: 12px"><LI><strong style="COLOR: #004999" >Microsoft Access</STRONG> and <strong style="COLOR: #004999">Microsoft Excel </STRONG> <LI><strong style="COLOR: #004999" >Microsoft Visual Basic</STRONG> and <strong style="COLOR: #004999">Microsoft Visual C++</STRONG> <LI><strong style="COLOR: #004999" >Microsoft ASP</STRONG> <LI><strong style="COLOR: #004999" >Borland Delphi</STRONG> and <strong style="COLOR: #004999">Borland C++ Builder</STRONG></LI></UL></LI></UL> <h3 style="COLOR: #004999"><em>No limits!</EM></H3> <p style="FONT-SIZE: 12px">Once equipped with Xpertdoc Studio, you will be able to push the limits of volume, complexity, performance and data-source access.</P> <div align="center"><h3 style="COLOR: #004999"><em>Free download and more information available at</EM></H3></DIV> <div align="center"><h3 style="COLOR: #004999"> <a href="http://www.xpertdoc.com" style="COLOR: #004999">www.xpertdoc.com</A></H3></DIV> <div align="center" style="FONT-SIZE: 12px"><p style="COLOR: #656565">Epsilon Technologies Inc. 1200, Blvd. Chomedey Suite 105<br> Laval, Quebec H7V 3Z3 Canada</P></DIV> <HR size="1" width="100%" noshade> <p style="FONT-SIZE: 11px; FONT-FAMILY: arial,sans-serif" >This message has been sent in accordance with Bill 301, paragraph (a)(2)(C) of S. 1618</P> <p style="FONT-SIZE: 11px; FONT-FAMILY: arial,sans-serif" >If you do not which to receive additional communications from the sender:</P> <ol style="FONT-SIZE: 11px; FONT-FAMILY: arial,sans-serif" > <li style="FONT-SIZE: 11px; FONT-FAMILY: arial,sans-serif" >Click on the reply button. <A href="mailto:r.d...@af..." ><img src="http://www.cirai.com/communiques/chabot/reply.gif" width="55" height="15" alt="" border="0"></A> <li style="FONT-SIZE: 11px; FONT-FAMILY: arial,sans-serif" >Insert your e-mail address in the subject field. <li style="FONT-SIZE: 11px; FONT-FAMILY: arial,sans-serif" >Click on the send button. </LI></OL> <p style="FONT-SIZE: 11px; FONT-FAMILY: arial,sans-serif" >This message is not intended for residents of the State of Washington. Addresses were screened to the best of our technical abilities. </P></TD></TR></TABLE></TD></TR></TABLE> </body> </html> |
From: Pier A. G. <pgu...@an...> - 2002-06-11 06:34:36
|
> > It may be due to the confusion of the string to use to describe the > driver. In some places it is 'OdbcJdbc'. In other places it is > 'Firebird/InterBase(r) driver'. I think we should be using the latter > throughout. > > Try changing the registry entry and let us lnow if it works. > Paul, you are right. By assigning: HKEY_CURRENT_USER\Software\Seagate Software\Crystal Reports\DatabaseOptions\OuterJoin = "odbcjdbc 'Firebird/InterBase(r) driver'" both old and new driver works correctly. Thanks. Pier Alberto GUIDOTTI |
From: Carlos G.A. <car...@ho...> - 2002-06-10 19:57:10
|
Hello: when creating a remote-view with visual foxpro, the SQLPrepare() is not called with the correct sql-statement. The driver always prepends "SYSDBA." before the specific table. eg: SELECT * FROM SYSDBA.TEST instead of: SElECT * FROM TEST This is corrent only if you don´t check the box "All user tables" ( todas las tablas de usuario ) and then select the table form create the view. Best Regards Carlos Guzmán Álvarez >From: sc...@de... >To: fir...@li... >Subject: [Firebird-odbc-devel] Creating, Editing Remote-Views with FoxPro >Date: Fri, 7 Jun 2002 10:16:32 +0200 > >Hi, > >when creating a remote-view with visual foxpro, the SQLPrepare() >is not called with the correct sql-statement. >The driver always prepends "SYSDBA." before the specific table. >eg: > SELECT * FROM SYSDBA.TEST >instead of: > SElECT * FROM TEST > >... >I guess the username was used (putted before the relationname), >but how could it happen? >--> >The statement was formed by VFP, but this only happens with this driver . >Which >method/function tells VFP to do so?. >----- >A last another proposal concerning VFP-Views: > >in ODBCStatement.cpp line794ff: > >use this code: >RETCODE OdbcStatement::sqlNumResultCols(SWORD * columns) >{ > clearErrors(); > > if (!resultSet ){ > // if the resultSet does not exist, execute it, to get a valid resultSet > // Foxpro calls this function to get all column-descriptions for its > // remote-views. > // This fixes the bug : ' I can't edit my remote-views in Visial FoxPro' > this->executeStatement(); > } > > ..... > >--------- >If someone has a better idea to get a valid resulSet ... please let me know > > > >_______________________________________________________________ > >Don't miss the 2002 Sprint PCS Application Developer's Conference >August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > >_______________________________________________ >Firebird-odbc-devel mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel _________________________________________________________________ Únase con MSN Hotmail al servicio de correo electrónico más grande del mundo. http://www.hotmail.com |
From: Paul R. <pr...@ib...> - 2002-06-10 16:26:36
|
Pier Alberto GUIDOTTI wrote: > I'm testing the latest changes with Crystal Reports 8.5. > I've seen a strange behaviour when using OUTER JOINS. > With previous version of the driver, OUTER JOINS were treated in the right > way by adding the following key in the registry: > > HKEY_CURRENT_USER\Software\Seagate Software\Crystal > Reports\DatabaseOptions\OuterJoin = 'odbcjdbc'. > > I downloaded the latest changes from CVS tree and recompiled them. Then I > tested the driver with Crystal. > Now OUTER JOINS are treated in a bad way, like this: > > SELECT > PERSON1.CODICE, PERSON1.NOME, > ENTI1.CODICE, ENTI1.DESCRIZION > FROM > { oj PERSON PERSON1 LEFT OUTER JOIN ENTI ENTI1 ON > PERSON1.ENTE = ENTI1.CODICE} > > The Oj operator is added to the query. It seems the registry key is ignored > by Crystal with the new version of driver, but why? > It may be due to the confusion of the string to use to describe the driver. In some places it is 'OdbcJdbc'. In other places it is 'Firebird/InterBase(r) driver'. I think we should be using the latter throughout. Try changing the registry entry and let us lnow if it works. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Paul S. <pa...@tr...> - 2002-06-10 12:16:01
|
Crystal Reports makes use of a set of functions, that look like this: ORDERS."OR_DTTM" >= {ts '2002-06-09 19:48:26.00'} I think the three are {ts} {dt} and {tm} How difficult would it be to implement these functions, and if it's fairly easy, where it code would it go? I don't mind writing a few lines of code.... Paul Schmidt, President Tricat Technologies pa...@tr... www.tricattechnologies.com |
From: Pier A. G. <pgu...@an...> - 2002-06-10 09:17:27
|
I'm testing the latest changes with Crystal Reports 8.5. I've seen a strange behaviour when using OUTER JOINS. With previous version of the driver, OUTER JOINS were treated in the right way by adding the following key in the registry: HKEY_CURRENT_USER\Software\Seagate Software\Crystal Reports\DatabaseOptions\OuterJoin = 'odbcjdbc'. I downloaded the latest changes from CVS tree and recompiled them. Then I tested the driver with Crystal. Now OUTER JOINS are treated in a bad way, like this: SELECT PERSON1.CODICE, PERSON1.NOME, ENTI1.CODICE, ENTI1.DESCRIZION FROM { oj PERSON PERSON1 LEFT OUTER JOIN ENTI ENTI1 ON PERSON1.ENTE = ENTI1.CODICE} The Oj operator is added to the query. It seems the registry key is ignored by Crystal with the new version of driver, but why? Regards, Ing. Pier Alberto GUIDOTTI ANALYSIS s.r.l. Via Zanardi 403/23B 40131 BOLOGNA (ITALY) http://www.analysisbo.it |
From: Paul R. <pr...@ib...> - 2002-06-08 13:51:25
|
Carlos G.A. wrote: > Hello: > > I have the same problem but i solve it( partially because my solution > fails in a concret situation ) in other way than you, the problem is > caused because the driver only have access to the resultset of a > executed statement, your solution is correct but if you have a table > with a lot of records you have to wait to the finish of the execution of > it, the good solution is ( i think ) make that the driver have access to > the resulted of the prepared statement. I just got around to reading this after I had posted Bernard's fix. I think you are probably right that there is a better solution than executeStatement(). In the meantime, anything is probably better than nothing. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Paul R. <pr...@ib...> - 2002-06-08 13:04:59
|
sc...@de... wrote: > A last another proposal concerning VFP-Views: I've committed this change, too. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Paul R. <pr...@ib...> - 2002-06-08 11:36:58
|
All, I've just updated the tree with recent contributions from Robert Milharcic and Carlos Alvarez. Tests indicate that we still have a way to go before releasing a new snapshot, but I didn't want to sit on the changes any longer. Among the problems that I am encountering are that blob text reading still seems very broken if the blob is greater than 64k (or perhaps 32k - I haven't had a chance to verify.) Also, metadata queries still seem to need work - at least, the BDE has trouble getting back info for the DBExplorer. I rolled back a suggested change for reading VARCHARS. It relied on taking the length from XSQLVAR.SQLLEN. This value only indicates the size of the specified varchar column, not the actual length of the data stored in the column. Paul -- Paul Reeves http://www.ibphoenix.com Supporting users of Firebird and InterBase |
From: Carlos G.A. <car...@ho...> - 2002-06-07 20:28:26
|
Hello: I have the same problem but i solve it( partially because my solution fails in a concret situation ) in other way than you, the problem is caused because the driver only have access to the resultset of a executed statement, your solution is correct but if you have a table with a lot of records you have to wait to the finish of the execution of it, the good solution is ( i think ) make that the driver have access to the resulted of the prepared statement( i don´t post my code because i´m in a cyber and don´t have them ). Best Regards Carlos Guzmán Álvarez Vigo-España P.D: Sorry about my bad english but i´m spanish. >From: sc...@de... >To: fir...@li... >Subject: [Firebird-odbc-devel] Creating, Editing Remote-Views with FoxPro >Date: Fri, 7 Jun 2002 10:16:32 +0200 > >Hi, > >when creating a remote-view with visual foxpro, the SQLPrepare() >is not called with the correct sql-statement. >The driver always prepends "SYSDBA." before the specific table. >eg: > SELECT * FROM SYSDBA.TEST >instead of: > SElECT * FROM TEST > >... >I guess the username was used (putted before the relationname), >but how could it happen? >--> >The statement was formed by VFP, but this only happens with this driver . >Which >method/function tells VFP to do so?. >----- >A last another proposal concerning VFP-Views: > >in ODBCStatement.cpp line794ff: > >use this code: >RETCODE OdbcStatement::sqlNumResultCols(SWORD * columns) >{ > clearErrors(); > > if (!resultSet ){ > // if the resultSet does not exist, execute it, to get a valid resultSet > // Foxpro calls this function to get all column-descriptions for its > // remote-views. > // This fixes the bug : ' I can't edit my remote-views in Visial FoxPro' > this->executeStatement(); > } > > ..... > >--------- >If someone has a better idea to get a valid resulSet ... please let me know > > > >_______________________________________________________________ > >Don't miss the 2002 Sprint PCS Application Developer's Conference >August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > >_______________________________________________ >Firebird-odbc-devel mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel _________________________________________________________________ MSN Photos es la manera más sencilla de compartir e imprimir sus fotos: http://photos.msn.com/support/worldwide.aspx |