Recent

Author Topic: dblib.dll  (Read 37151 times)

BigChimp

  • Hero Member
  • *****
  • Posts: 5740
  • Add to the wiki - it's free ;)
    • FPCUp, PaperTiger scanning and other open source projects
Re: dblib.dll
« Reply #15 on: July 04, 2013, 04:50:09 pm »
Even if they could legally include the dll there is no way to know which SQLServer version your running and dll's usually change with the server version it is connecting to.
Nope, because the TDS protocol hasn't changed (that much). FreeTDS connects to a lot of different versions of MSSQL, as well as Sybase ASE.
Want quicker answers to your questions? Read http://wiki.lazarus.freepascal.org/Lazarus_Faq#What_is_the_correct_way_to_ask_questions_in_the_forum.3F

Open source including papertiger OCR/PDF scanning:
https://bitbucket.org/reiniero

Lazarus trunk+FPC trunk x86, Windows x64 unless otherwise specified

BigChimp

  • Hero Member
  • *****
  • Posts: 5740
  • Add to the wiki - it's free ;)
    • FPCUp, PaperTiger scanning and other open source projects
Re: dblib.dll
« Reply #16 on: July 04, 2013, 04:56:21 pm »
Can't this dll be included with lazarus so it is made available when using these components ?

You are welcome to file a feature request via the bug tracker... however:
1. Where shall we stop? Ship all Firebird, PostgreSQL etc dlls as well? If Oracle was open source, what about including the 100s of megs of the so-called Instant Client dlls?
2. This won't help much in getting the dll included in your application directory. A solution, installing in your Windows system directory, won't help when your customers get the application and miss the DLL.

Given that, I'd just put dblib.dll in the appropriate windows system (32 or 64 bits depending on DLL) directory of your dev machine and forget about it (except of course when distributing your database programs to others).
Want quicker answers to your questions? Read http://wiki.lazarus.freepascal.org/Lazarus_Faq#What_is_the_correct_way_to_ask_questions_in_the_forum.3F

Open source including papertiger OCR/PDF scanning:
https://bitbucket.org/reiniero

Lazarus trunk+FPC trunk x86, Windows x64 unless otherwise specified

goodname

  • Sr. Member
  • ****
  • Posts: 297
Re: dblib.dll
« Reply #17 on: July 04, 2013, 08:21:12 pm »
Was not aware that someone had written a connection dll independent of MS. That changes the politics. Agree with BigChimp comments on this.

jack616

  • Sr. Member
  • ****
  • Posts: 266
Re: dblib.dll
« Reply #18 on: August 14, 2013, 01:31:20 pm »

Tip for configuring - applies to mySQL so I assume it does to others:

1. Stick with keeping the dll in the program directory (just keeps things simpler)
2. Ensure you have the correct release version of the dll eg mysql5.0 or mySql5.5  or whatevr db you use etc
that matches a) your program and b)your server and c) to the os you are compiling to
3. BIG tip - If compiling 32bit ensure you use the 32bit dll or 64bit dll when compiling with 64bit lazarus

It is very easy to get the wrong word size file. Also for mySQL people notice there may be 2 different
sized versions of the dll with the same name on your machine in different places - generally - ensure you use the big one.

Hope thats helpful.

BigChimp

  • Hero Member
  • *****
  • Posts: 5740
  • Add to the wiki - it's free ;)
    • FPCUp, PaperTiger scanning and other open source projects
Re: dblib.dll
« Reply #19 on: September 03, 2013, 01:09:36 pm »
Some good ideas, but some caveats as well ;)

Tip for configuring - applies to mySQL so I assume it does to others:
Assumptions are the mother of all... never mind.

1. Stick with keeping the dll in the program directory (just keeps things simpler)
This will bite you when trying to connect in design-time... as has been amply demonstrated in earlier posts on this thread.

Myself, I just copy my dll to the windows system directory on my dev machine and forget about it... except that you need to remember to put the dll in the program directory when giving the compiled program to other people.

2. Ensure you have the correct release version of the dll eg mysql5.0 or mySql5.5  or whatevr db you use etc
that matches a) your program and b)your server and c) to the os you are compiling to
This advice is invalid for MySQL as well: re b): your mysql *CLIENT* dll version should match the unit name in your FPC code. The client version can differ from the server version (though it's up to mysql to indicate what's supported).

For MS SQL Server/Sybase ASE with FreeTDS dlls, it's recommended to use a fairly recent dll, e.g. the one provided as a courtesy on the FPC server (see links elsewhere). That single DLL should work for MS SQL 2000..2008 and probably 2012 (and probably really old versions) and Sybase ASE at least 12.5..15.

3. BIG tip - If compiling 32bit ensure you use the 32bit dll or 64bit dll when compiling with 64bit lazarus
Yes, that completely applies to FreeTDS dlls as well (in fact, AFAIU any dlls on Windows should match bitness with the program that calls them)

Thanks,
BigChimp
« Last Edit: September 03, 2013, 01:13:17 pm by BigChimp »
Want quicker answers to your questions? Read http://wiki.lazarus.freepascal.org/Lazarus_Faq#What_is_the_correct_way_to_ask_questions_in_the_forum.3F

Open source including papertiger OCR/PDF scanning:
https://bitbucket.org/reiniero

Lazarus trunk+FPC trunk x86, Windows x64 unless otherwise specified

ikutluay

  • New Member
  • *
  • Posts: 18
Re: dblib.dll
« Reply #20 on: September 16, 2013, 03:50:24 pm »
Hello.. Can i use the 32bit dblib.dll on my wince device? it is m3 mobile arm processor device....

wince version is 5.

LacaK

  • Hero Member
  • *****
  • Posts: 600
Re: dblib.dll
« Reply #21 on: September 18, 2013, 06:04:32 am »
Can i use the 32bit dblib.dll on my wince device?
No, from this location ftp://ftp.freepascal.org/fpc/contrib/windows/
There are versions precompiled for Win32 and Win64 targets , not for WinCE

 

TinyPortal © 2005-2018