firebird-odbc-devel — All about development of Firebird ODBC driver donated by IBPhoenix

Re: [Firebird-odbc-devel] [Firebird-checkins] CVS: OdbcJdbc MbsAndWcs.cpp, 1.1.2.3, 1.1.2.3.2.1

[Alexander P. <ale...@re...>]

Nikolay Samofatov wrote:
> 2. As I indicated privately earlier, the patch you committed seems to
> create a potential buffer overflow.
>
> I read both specs and to implement Unix wcstombs properly using Windows'
> WideCharToMultiByte the following logic is necessary:
>
> Index: MbsAndWcs.cpp
> ===================================================================
> --- MbsAndWcs.cpp    (revision 4020)
> +++ MbsAndWcs.cpp    (working copy)
> @@ -47,10 +47,10 @@
>                                       wcstr,
>                                       -1,
>                                       (LPSTR)mbstr,
> -                                      !mbstr ? 0 : (int)count+1,
> +                                      !mbstr ? 0 : (int)count,
>                                       NULL,
>                                       NULL );
> -    if ( len > 0 )
> +    if ( len > 0 && (!mbstr || len != count || !mbstr[count-1]) )
>         len--;
>
>     return len;
>
> Please somebody correct me if I am wrong.
>
>   
Nikolay, in your code _WcsToMbs will return 0 for some cases and the 
following code will not work correctly (there is a similar logic in ODBC 
driver):
   
wchar_t wstr[5] = L"test";
int len = WcsToMbs(NULL, wstr, 0);
char* str = new char[len+1];
len = WcsToMbs(str, wstr, wcslen(wstr));
str[len] = '\0';
cout << str;

If you will see a real example of case with buffer overflow then please 
show it. I looked a code and I have not seen potential problems with it.

Alexander
-- 
Alexander Potapchenko
http://www.red-soft.biz
Senior developer

Re: [Firebird-odbc-devel] [Firebird-checkins] CVS: OdbcJdbc MbsAndWcs.cpp, 1.1.2.3, 1.1.2.3.2.1

[Nikolay S. <nik...@re...>]

Roman,

1. All patches committed to older branches (e.g. B2_0_0 in this case)
should go to HEAD as well.
This should be the case for all public as well as Red Soft private trees.

2. As I indicated privately earlier, the patch you committed seems to
create a potential buffer overflow.

I read both specs and to implement Unix wcstombs properly using Windows'
WideCharToMultiByte the following logic is necessary:

Index: MbsAndWcs.cpp
===================================================================
--- MbsAndWcs.cpp    (revision 4020)
+++ MbsAndWcs.cpp    (working copy)
@@ -47,10 +47,10 @@
                                      wcstr,
                                      -1,
                                      (LPSTR)mbstr,
-                                      !mbstr ? 0 : (int)count+1,
+                                      !mbstr ? 0 : (int)count,
                                      NULL,
                                      NULL );
-    if ( len > 0 )
+    if ( len > 0 && (!mbstr || len != count || !mbstr[count-1]) )
        len--;

    return len;

Please somebody correct me if I am wrong.

Roman Simakov wrote:
> Update of /cvsroot/firebird/OdbcJdbc
> In directory sc8-pr-cvs17.sourceforge.net:/tmp/cvs-serv327
>
> Modified Files:
>       Tag: B2_0_0
> 	MbsAndWcs.cpp 
> Log Message:
> Fix for ODBC-32 (32 Access-related multi DB problem) from Alexander Potapchenko.
>
> Index: MbsAndWcs.cpp
> ===================================================================
> RCS file: /cvsroot/firebird/OdbcJdbc/MbsAndWcs.cpp,v
> retrieving revision 1.1.2.3
> retrieving revision 1.1.2.3.2.1
> diff -b -U3 -r1.1.2.3 -r1.1.2.3.2.1
> --- MbsAndWcs.cpp	4 Sep 2007 14:52:47 -0000	1.1.2.3
> +++ MbsAndWcs.cpp	1 Sep 2008 10:51:54 -0000	1.1.2.3.2.1
> @@ -47,7 +47,7 @@
>  									  wcstr,
>  									  -1,
>  									  (LPSTR)mbstr,
> -									  !mbstr ? 0 : (int)count,
> +									  !mbstr ? 0 : (int)count+1,
>  									  NULL,
>  									  NULL );
>  	if ( len > 0 )
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Firebird-checkins mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-checkins
>   


-- 
Nikolay Samofatov, MBA
Red Soft International
+1 416 710 6854

[Firebird-odbc-devel] Too many download options

[Jorge A. B. <li...@da...>]

I think download page is overloaded, why offer so many options? (1.2, 
1.2.1, 1.3, 2.0). 2.0.146 is pretty stable now, when an installer is 
deployed should be the only choice (at lest in frontpage, provide a 
"archive" section if you want to offer all those old builds).

Changelog should point to actual CVS file, as it is now updated.

Regards

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Jorge A. B. <li...@da...>]

Two suggestions:

- Make a build available from official site
- Mark resolved issues as resolved in tracker

Thanks

Alexander Potapchenko escribió:
> Hi, all!
>
> I made some patches for OdbcJdbc B2_0_0 branch.
>
> odbc-32.patch fixes http://tracker.firebirdsql.org/browse/ODBC-32.
> odbc-23.patch fixes http://tracker.firebirdsql.org/browse/ODBC-23.
> odbc-x64.patch for support x64 building.
> Goals of odbc-install.patch are:
> 1) Renaming driver from OdbcFb32 (OdbcFb64) to OdbcFb (This is more
> correctly because x64 and x86 (Windows or Linux) libraries have
> identical names in most cases).
> 2) Code corrections (fixed usage of old hard coded "OdbcJdbcSetup" in
> different places).
> 3) Installation corrections. Now if you install driver DLL by hand using
> regsvr32.exe with key "/i" then it will be installed into system
> directory. If key "/i" is not used then driver will be registered in the
> directory where it is located.
>
> I made a snapshot build (146) too. You can find it here:
> http://www.red-soft.biz/files/downloads/diff/OdbcFb_2.0.0.146_x86_x64.zip
>
> We'd like to commit these patches (Red Soft). Are there any objections?
>
> Regards,
> Alexander Potapchenko,
> Red Soft Corporation
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Paul R. <pr...@ib...>]

On Thursday 28 August 2008, Alexander Potapchenko wrote:
>
> After confirmation our patches I can improve official ODBC installer
> (For example, it is possible to make 32-bit and 64-bit drivers
> registration in one installer if this is necessary)

Yes, I think it  is necessary. The intention behind the AMD64 architecture 
is that everything should just 'work'. To me this means that a 64-bit kit 
should include a 32-bit kit. 

What do others think?


Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Specialists in Firebird support

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Paul R. <pr...@ib...>]

On Wednesday 27 August 2008, Alexander Potapchenko wrote:
>
> Yes of course,  but I don't understand meaning of '32' suffix in
> Firebird ODBC dirver case.

I am not bothered about the '32' - just about the fact that we have already 
changed the driver name once and we are now planning to change it again.

Anyway, if no-one else objects then lets change it. 


Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Specialists in Firebird support

[Firebird-odbc-devel] driver question

[Heine F. <hei...@gm...>]

Hi

Are you going to support dynamic and keyset cursors any time in the future?
As far as I know you currently only support static cursors.
That is quite limiting for evnvironments like VB and Access (VBA).

Thanks

Heine Ferreira

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Jorge A. B. <li...@da...>]

Read on a forum:

"It's important to understand which kind of DSN you have. On an x64 system,
you can create an ODBC connection(DSN) on the 32-bit side of the system or
on the 64-bit side of the system.

32-bit applications will only see ODBC connections created in the 32-bit
side, and 64-bits applications will only see ODBC connections from the
64-bit side. Each kind of application has is own registry.

To setup DSN for 32-bit application you must use:
%WINDIR%\SysWOW64\odbcad32.exe
and for 64-bit application you must use:
%WINDIR%\System32\odbcad32.exe"

Ok, MS has done it, even for ODBC admin, but naming 64 bit driver like a 
32 bit one ... seems weird to me. I prefer OdbcFb.dll, like the MySQL 
ones (unique name, no "32" for both platforms)

Regards

Alexander Potapchenko escribió:
> Paul Reeves wrote:
>> On Wednesday 27 August 2008:
>>
>> Anyway, it was a mistake to name the odbc driver libraries differently 
>> depending upon processor target. That should be fixed. The question is 
>> whether, for Windows, we should follow the convention and name the driver 
>> OdbcFb32. Above all, this would help users who have not yet migrated to 
>> 64-bits.
>>
>>   
>> Apart from the naming issue, I think it would be great to see these 
>> patches committed.
>> Paul
>>   
> It is possible to name 64-bit driver as OdbcFb32.dll. It is not 
> required more work (in the installer, docs and in other places).
> If you agree with it and other changes we can commit patches (we have 
> all rights on a commit to CVS repository).
>
> Regards,
> Alexander Potapchenko,
> Red Soft Corporation
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>   

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Alexander P. <ale...@re...>]

Paul Reeves wrote:
> On Wednesday 27 August 2008:
>
> Anyway, it was a mistake to name the odbc driver libraries differently 
> depending upon processor target. That should be fixed. The question is 
> whether, for Windows, we should follow the convention and name the driver 
> OdbcFb32. Above all, this would help users who have not yet migrated to 
> 64-bits.
>
>   
> Apart from the naming issue, I think it would be great to see these 
> patches committed.
> Paul
>   
It is possible to name 64-bit driver as OdbcFb32.dll. It is not required 
more work (in the installer, docs and in other places).
If you agree with it and other changes we can commit patches (we have 
all rights on a commit to CVS repository).

Regards,
Alexander Potapchenko,
Red Soft Corporation

Re: [Firebird-odbc-devel] Patches for Odbc driver

[André K. C. <Kna...@be...>]

~~~Ihre Nachricht~~~

PR> ...system32 directory contains 64-bit binaries if the O/S is 64-bit. (And what
PR> genius decided that the 32-bit binaries should be stored in WOW64?)

Indeed, one of the major reasons for support calls... users read in
any "installation guide" to copy any dll to the "system32" folder,
which they do, and the software - surprise, surprise - will not run.

The one who decided for this architecture probably is just the poor
victim of badly designed legacy programs. Probably a lot of hardcoded
paths in some MS libraries :)

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Alexander P. <ale...@re...>]

Jorge Andrés Brugger wrote:
> Install changes shouldn't affect setup creators, right? (I use Innosetup 
> and register the driver with InnoSetup own "regserver" flag)
If you use this command to register ODBC driver
[Run]
;Filename: {sys}\regsvr32.exe; Parameters: "/s ""{app}""\OdbcFb32.dll";
than the driver will not be copied to the system directory and Odbc 
Driver Manager will be use the driver from the installation folder (for 
example: C:\Program Files (x86)\Firebird\Firebird_ODBC).
For example Oracle ODBC driver is registered in this way.
And the code:
[UninstallDelete]
Type: Files; Name: {sys}\OdbcFb32.dll; Components: DeveloperComponent is 
not required in this case.

You can use this command:
;Filename: {sys}\regsvr32.exe; Parameters: "/s /i ""{app}""\OdbcFb32.dll";
for old installation rules.

After confirmation our patches I can improve official ODBC installer 
(For example, it is possible to make 32-bit and 64-bit drivers 
registration in one installer if this is necessary)

Regards,
Alexander Potapchenko,
Red Soft Corporation

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Alexander P. <ale...@re...>]

Paul Reeves wrote:
> Basically, if a 32 bit library is called OdbcFb32 then the 64-bit library 
> should be called that too. The O/S manages the installation and loading. 
> Applications compiled for 32-bit can be recompiled for 64-bit without any 
> changes (well, not to library names, anyway.)
>   
Yes of course,  but I don't understand meaning of '32' suffix in 
Firebird ODBC dirver case.
Name OdbcFb32.dll appeared only in 2.0 branch and I think that this name 
is not correctly because there are no applications which important such 
name of the driver.
There are many x64 and x86 libraries developed by Microsoft in the 
system directory (system32/SysWOW64) with identical names and without 
'32' suffix (except old important  libraries for most applications 
(shell32.dll, gdi32.dll and others)).

Regards,
Alexander Potapchenko,
Red Soft Corporation

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Paul R. <pr...@ib...>]

On Wednesday 27 August 2008, Alexander Potapchenko wrote:

> Goals of odbc-install.patch are:
> 1) Renaming driver from OdbcFb32 (OdbcFb64) to OdbcFb (This is more
> correctly because x64 and x86 (Windows or Linux) libraries have
> identical names in most cases).

This needs fixing, but I'm not sure that renaming to OdbcFb is correct for 
Windows. Microsoft went to a lot of trouble so that nothing needs to be 
renamed at all. Not sure if that should be a :-) or a :-(

Basically, if a 32 bit library is called OdbcFb32 then the 64-bit library 
should be called that too. The O/S manages the installation and loading. 
Applications compiled for 32-bit can be recompiled for 64-bit without any 
changes (well, not to library names, anyway.)

This is confusing, because it was Microsoft that started the tradition of 
suffixing binaries with the 'bitness' of the processor. And now the 
system32 directory contains 64-bit binaries if the O/S is 64-bit. (And what 
genius decided that the 32-bit binaries should be stored in WOW64?) But all 
of that really becomes irrelevant, because the O/S works it all out. 

Anyway, it was a mistake to name the odbc driver libraries differently 
depending upon processor target. That should be fixed. The question is 
whether, for Windows, we should follow the convention and name the driver 
OdbcFb32. Above all, this would help users who have not yet migrated to 
64-bits.


>
> We'd like to commit these patches (Red Soft). Are there any objections?
>

Apart from the naming issue, I think it would be great to see these patches 
committed.


Paul
-- 
Paul Reeves
http://www.ibphoenix.com
Specialists in Firebird support

Re: [Firebird-odbc-devel] Patches for Odbc driver

[Jorge A. B. <li...@da...>]

Good news Alexander!

Microsoft uses differents names for 32 or 64 bit drivers, but if a 32 
bit app should run fine in x64 system using 64 bits driver, I agree with 
unifying the name.

Install changes shouldn't affect setup creators, right? (I use Innosetup 
and register the driver with InnoSetup own "regserver" flag)

Regards!

Alexander Potapchenko escribió:
> Hi, all!
>
> I made some patches for OdbcJdbc B2_0_0 branch.
> I made a snapshot build (146) too. You can find it here (and patches):
> http://www.red-soft.biz/files/downloads/diff/OdbcFb_2.0.0.146_x86_x64.zip
>
> odbc-32.patch fixes http://tracker.firebirdsql.org/browse/ODBC-32.
> odbc-23.patch fixes http://tracker.firebirdsql.org/browse/ODBC-23.
> odbc-x64.patch for support x64 building.
> Goals of odbc-install.patch are:
> 1) Renaming driver from OdbcFb32 (OdbcFb64) to OdbcFb (This is more
> correctly because x64 and x86 (Windows or Linux) libraries have
> identical names in most cases).
> 2) Code corrections (fixed usage of old hard coded "OdbcJdbcSetup" in
> different places).
> 3) Installation corrections. Now if you install driver DLL by hand using
> regsvr32.exe with key "/i" then it will be installed into system
> directory. If key "/i" is not used then driver will be registered in the
> directory where it is located.
>
> We'd like to commit these patches (Red Soft). Are there any objections?
>
> Regards,
> Alexander Potapchenko,
> Red Soft Corporation
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel
>
>
>   

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

[Firebird-odbc-devel] Patches for Odbc driver

[Alexander P. <ale...@re...>]

Hi, all!

I made some patches for OdbcJdbc B2_0_0 branch.
I made a snapshot build (146) too. You can find it here (and patches):
http://www.red-soft.biz/files/downloads/diff/OdbcFb_2.0.0.146_x86_x64.zip

odbc-32.patch fixes http://tracker.firebirdsql.org/browse/ODBC-32.
odbc-23.patch fixes http://tracker.firebirdsql.org/browse/ODBC-23.
odbc-x64.patch for support x64 building.
Goals of odbc-install.patch are:
1) Renaming driver from OdbcFb32 (OdbcFb64) to OdbcFb (This is more
correctly because x64 and x86 (Windows or Linux) libraries have
identical names in most cases).
2) Code corrections (fixed usage of old hard coded "OdbcJdbcSetup" in
different places).
3) Installation corrections. Now if you install driver DLL by hand using
regsvr32.exe with key "/i" then it will be installed into system
directory. If key "/i" is not used then driver will be registered in the
directory where it is located.

We'd like to commit these patches (Red Soft). Are there any objections?

Regards,
Alexander Potapchenko,
Red Soft Corporation

[Firebird-odbc-devel] Patches for Odbc driver

[Alexander P. <ale...@re...>]

Hi, all!

I made some patches for OdbcJdbc B2_0_0 branch.

odbc-32.patch fixes http://tracker.firebirdsql.org/browse/ODBC-32.
odbc-23.patch fixes http://tracker.firebirdsql.org/browse/ODBC-23.
odbc-x64.patch for support x64 building.
Goals of odbc-install.patch are:
1) Renaming driver from OdbcFb32 (OdbcFb64) to OdbcFb (This is more
correctly because x64 and x86 (Windows or Linux) libraries have
identical names in most cases).
2) Code corrections (fixed usage of old hard coded "OdbcJdbcSetup" in
different places).
3) Installation corrections. Now if you install driver DLL by hand using
regsvr32.exe with key "/i" then it will be installed into system
directory. If key "/i" is not used then driver will be registered in the
directory where it is located.

I made a snapshot build (146) too. You can find it here:
http://www.red-soft.biz/files/downloads/diff/OdbcFb_2.0.0.146_x86_x64.zip

We'd like to commit these patches (Red Soft). Are there any objections?

Regards,
Alexander Potapchenko,
Red Soft Corporation

Re: [Firebird-odbc-devel] Wrong PK detected (MS Access 2003)

[bill l. <cbi...@gm...>]

Jorge Andrés Brugger wrote:
> Attached is a Firebird 2.0.4 backup.
> 
> - Restore the backup
> - Create a ODBC DSN with standard options.
> - Create or use an existing MS Access 2003 DB
> - Link the only one table available
> 
> In Firebird, PK of the table is the "codigo" field. But Access set 
> "Descripcion" as PK (what is wrong, Descripcion isn't even unique).
> 

It is interesting. Is there any generic odbc api that returns PK or index?

regards,

[Firebird-odbc-devel] [Fwd: [Firebird-checkins] CVS: OdbcJdbc/IscDbc IscStatement.cpp, 1.18.2.15, 1.18.2.16]

[Jorge A. B. <li...@da...>]

I think this change is the origin of 
http://tracker.firebirdsql.org/browse/ODBC-32

(it´s the only change between builds 142 and 143, build 142 works fine, 
144-145 doesn't)

-------- Mensaje original --------
Asunto: 	[Firebird-checkins] CVS: OdbcJdbc/IscDbc IscStatement.cpp, 
1.18.2.15, 1.18.2.16
Fecha: 	Sun, 26 Aug 2007 10:21:09 -0700
De: 	Vladimir Tsvigun <pr...@us...>
A: 	fir...@li...



Update of /cvsroot/firebird/OdbcJdbc/IscDbc
In directory sc8-pr-cvs17:/tmp/cvs-serv19934

Modified Files:
      Tag: v2-0-beta
	IscStatement.cpp 
Log Message:
- fixed bug, URL: http://tracker.firebirdsql.org/browse/ODBC-29,
 "status_exception thrown and caught on every access due to trying 
  to close already closed cursor", branch v2-0-beta

Index: IscStatement.cpp
===================================================================
RCS file: /cvsroot/firebird/OdbcJdbc/IscDbc/IscStatement.cpp,v
retrieving revision 1.18.2.15
retrieving revision 1.18.2.16
diff -b -U3 -r1.18.2.15 -r1.18.2.16
--- IscStatement.cpp	22 Mar 2007 17:44:27 -0000	1.18.2.15
+++ IscStatement.cpp	26 Aug 2007 17:21:05 -0000	1.18.2.16
@@ -559,8 +559,6 @@
 	resultSets.deleteItem (resultSet);
 	if (resultSets.isEmpty())
 	{
-		openCursor = false;
-		typeStmt = stmtNone;
 		if ( connection )
 		{
 			if ( transactionLocal )
@@ -570,14 +568,21 @@
 			}
 			else if ( connection->transactionInfo.autoCommit )
 				connection->commitAuto();
+
+			if ( isActiveCursor() )
+			{
 			// Close cursors too.
 			ISC_STATUS statusVector[20];
 			connection->GDS->_dsql_free_statement( statusVector, &statementHandle, DSQL_close );
 			// Cursor already closed or not assigned
-			if ( statusVector[1] && statusVector[1] != 335544569 )
+				if ( statusVector[1] && statusVector[1] != 335544569)
 				THROW_ISC_EXCEPTION (connection, statusVector);
 		}
 	}
+
+		openCursor = false;
+		typeStmt = stmtNone;
+	}
 }
 
 void IscStatement::prepareStatement(const char * sqlString)


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Firebird-checkins mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-checkins




-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

Re: [Firebird-odbc-devel] Odbc driver build 2.0.145 (for testing)

[Jorge A. B. <li...@da...>]

I've attached two additional log files to 
http://tracker.firebirdsql.org/browse/ODBC-32 , much smaller than 
original ones.

I´ll appreciate if someone can see them. I suppose this behaviour is 
caused to a minimal change introduced in build 144.

Thanks!

Jorge Andrés Brugger escribió:
> I´ve tried to check if it fixes 
> http://tracker.firebirdsql.org/browse/ODBC-32 (project 2003 fixes maybe 
> fix my problem, I tough). Unfortunately, it doesn't :)
>
> Nikolay Samofatov escribió:
>   
>> Hi, All!
>>
>> A few people asked me privately to provide them Firebird ODBC driver 
>> with the most recent changes and install instructions.
>> So I decided to make and publish a snapshot build instead.
>>
>> You can find it here:
>> http://firebird.sourceforge.net/download/odbc_test/OdbcFb_v2_0_145_Win32.zip
>>
>> To install you can either use the official 2.0 installer, and replace 
>> the DLL with new one. Or you can install driver DLL by hand:
>> 0. Uninstall Firebird or Red Database ODBC driver if one was installed 
>> earlier using installer (to avoid possible confusion later)
>> 1. Unpack OdbcFb32.dll to some temporary folder (NOT Windows\System32 or 
>> SysWOW64)
>> 2. Run "...Windows\System32[or SysWOW64 if on x64]\regsvr32.exe /i 
>> OdbcFb32.dll". If on Vista you need to do this in elevated command 
>> prompt. This will copy DLL to appropriate Windows system directory.
>> If on 64-bit box, you than need to run SysWOW64\odbcad32.exe manually to 
>> configure 32-bit DSN.  ODBC control panel applet only controls 64-bit ODBC.
>>
>> The changes in this build are:
>>
>> 145)    - current BUILDNUM_VERSION set 145 ( 10 Sep 2008 )
>>     - Fix ODBC driver to work correctly with Microsoft Project 2003. 
>> This involves the following changes:
>>       - Implement basic support for SQL_GUID data type
>>       - Implement partial column binding. Previously, if NULL buffer 
>> pointer and non-null
>>         indicator variable were passed to SQLBindCol the driver crashed.
>>       These changes make Project 2003 save and load projects from 
>> Firebird databases correctly
>>       thanks to Nikolay Samofatov
>>     - Re-organize cvs tree for ODBC driver
>>       Make branch naming conform more closely to standard used for 
>> Firebird tree
>>       thanks to Paul Reeves
>>     - Fix 'invalid parameter in transaction parameter block' error with 
>> Firebird 2.1
>>       thanks to Nikolay Samofatov
>>     - Fix DSN configuration dialog crashes due to double-free bugs in 
>> users management code
>>       thanks to Nikolay Samofatov
>>
>>   
>>     
>
>   

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

[Firebird-odbc-devel] Wrong PK detected (MS Access 2003)

[Jorge A. B. <li...@da...>]

Attached is a Firebird 2.0.4 backup.

- Restore the backup
- Create a ODBC DSN with standard options.
- Create or use an existing MS Access 2003 DB
- Link the only one table available

In Firebird, PK of the table is the "codigo" field. But Access set 
"Descripcion" as PK (what is wrong, Descripcion isn't even unique).

Some time ago a similar bug was reported and fixed by Vladimir. It's 
there again :)

I can enter details in tracker if needed.

Regards

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

Re: [Firebird-odbc-devel] Odbc driver build 2.0.145 (for testing)

[Jorge A. B. <li...@da...>]

I´ve tried to check if it fixes 
http://tracker.firebirdsql.org/browse/ODBC-32 (project 2003 fixes maybe 
fix my problem, I tough). Unfortunately, it doesn't :)

Nikolay Samofatov escribió:
> Hi, All!
>
> A few people asked me privately to provide them Firebird ODBC driver 
> with the most recent changes and install instructions.
> So I decided to make and publish a snapshot build instead.
>
> You can find it here:
> http://firebird.sourceforge.net/download/odbc_test/OdbcFb_v2_0_145_Win32.zip
>
> To install you can either use the official 2.0 installer, and replace 
> the DLL with new one. Or you can install driver DLL by hand:
> 0. Uninstall Firebird or Red Database ODBC driver if one was installed 
> earlier using installer (to avoid possible confusion later)
> 1. Unpack OdbcFb32.dll to some temporary folder (NOT Windows\System32 or 
> SysWOW64)
> 2. Run "...Windows\System32[or SysWOW64 if on x64]\regsvr32.exe /i 
> OdbcFb32.dll". If on Vista you need to do this in elevated command 
> prompt. This will copy DLL to appropriate Windows system directory.
> If on 64-bit box, you than need to run SysWOW64\odbcad32.exe manually to 
> configure 32-bit DSN.  ODBC control panel applet only controls 64-bit ODBC.
>
> The changes in this build are:
>
> 145)    - current BUILDNUM_VERSION set 145 ( 10 Sep 2008 )
>     - Fix ODBC driver to work correctly with Microsoft Project 2003. 
> This involves the following changes:
>       - Implement basic support for SQL_GUID data type
>       - Implement partial column binding. Previously, if NULL buffer 
> pointer and non-null
>         indicator variable were passed to SQLBindCol the driver crashed.
>       These changes make Project 2003 save and load projects from 
> Firebird databases correctly
>       thanks to Nikolay Samofatov
>     - Re-organize cvs tree for ODBC driver
>       Make branch naming conform more closely to standard used for 
> Firebird tree
>       thanks to Paul Reeves
>     - Fix 'invalid parameter in transaction parameter block' error with 
> Firebird 2.1
>       thanks to Nikolay Samofatov
>     - Fix DSN configuration dialog crashes due to double-free bugs in 
> users management code
>       thanks to Nikolay Samofatov
>
>   

-- 
Jorge Andrés Brugger
Informática
DASU - Obra Social del Personal de la Universidad Nacional de la Patagonia
Comodoro Rivadavia, Chubut, Argentina
Teléfono (0297) 446-4444 int. 103
Correo electrónico: jbr...@da...
Website: www.dasu.com.ar

Re: [Firebird-odbc-devel] Firbird from MSAccess via ODBC

[Georgi V. <geo...@br...>]

Hello,
Each table must have primary key.

Regards,
Georgi Varbanov

-----Original Message-----
From: fir...@li...
[mailto:fir...@li...] On Behalf Of Russ
Jones
Sent: Monday, August 04, 2008 9:03 PM
To: fir...@li...
Subject: [Firebird-odbc-devel] Firbird from MSAccess via ODBC

Hello,
  I've got a contact databse on Firebird 2.1 and want users to interact with

it via MSAccess.  I've downloaded the ODBC driver from IBPhoenix, installed 
and linked in some tables.  The tables show up in Access and I can add 
records.  However, when I edit a record or try to delete one, an error is 
returned.  The error message is something to the effect "another user has 
changed the record and you cannot save your your changes".  Yet there is 
only one connection the whole time, so no other user could have changed the 
record.
Has anyone run into this problem or perhaps have an idea what I'm doing 
wrong?



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Firebird-odbc-devel mailing list
Fir...@li...
https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

Re: [Firebird-odbc-devel] Firbird from MSAccess via ODBC

[tjelvar e. <tj...@fa...>]

I've run into that problem, hard to pinpoint down right away,
but for starters:

* Access doesn't like the triggers / contraints set in employee.fdb
Many tables just can't be updated.
Ther's one table (currencies i belive) that works fine, so start of  
there.

It's tedious that there's problems around the sp's / triggers when  
working
with access, try to stay away from them and use sp's (and direct  
queries)
from access when you need buissness logic).

Others may have better suggestions, but for starters, good luck with  
these tips.

ATB

//teson

11 aug 2008 kl. 12.28 skrev gpa...@k-...:

> bill lam a écrit :
>
>> IIRC someone had asked this before. It seems fbodbc does not  
>> support dynamic
>> cursor which is needed by msaccess.
>>
>
> I'm not an expert, but here is what I think anyway:
>
> - firebird (not especially fbodbc) don't support dynamic cursors. I
> think i have read about that in kinterbasdb docs.
>
> - msaccess can work without dynamic cursors - IIRC that's setup in the
> connection/recordset creation options.
>
> - the OP problem looks like a rounding error of a float field to me; I
> have seen something like that a long time ago.
> Maybe the OP could report if the problem occurs with a table having  
> only
> integer and string fields.
>
> Gerard Patel
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Firebird-odbc-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-odbc-devel

Re: [Firebird-odbc-devel] Firbird from MSAccess via ODBC

[<gpa...@k-...>]

bill lam a écrit :

> IIRC someone had asked this before. It seems fbodbc does not support dynamic 
> cursor which is needed by msaccess.
> 

I'm not an expert, but here is what I think anyway:

- firebird (not especially fbodbc) don't support dynamic cursors. I 
think i have read about that in kinterbasdb docs.

- msaccess can work without dynamic cursors - IIRC that's setup in the 
connection/recordset creation options.

- the OP problem looks like a rounding error of a float field to me; I 
have seen something like that a long time ago.
Maybe the OP could report if the problem occurs with a table having only 
integer and string fields.

Gerard Patel

Re: [Firebird-odbc-devel] Firbird from MSAccess via ODBC

[bill l. <cbi...@gm...>]

Russ Jones wrote:
> Hello,
>   I've got a contact databse on Firebird 2.1 and want users to interact with 
> it via MSAccess.  I've downloaded the ODBC driver from IBPhoenix, installed 
> and linked in some tables.  The tables show up in Access and I can add 
> records.  However, when I edit a record or try to delete one, an error is 
> returned.  The error message is something to the effect "another user has 
> changed the record and you cannot save your your changes".  Yet there is 
> only one connection the whole time, so no other user could have changed the 
> record.
> Has anyone run into this problem or perhaps have an idea what I'm doing 
> wrong?

IIRC someone had asked this before. It seems fbodbc does not support dynamic 
cursor which is needed by msaccess.

regards,