dblib.dll

[Zath]

My attempts at creating a MS SQL connection or ODBC connection keep failing sayin I need dblib.dll.
I have now managed to find it.
Excuse my ignorance but what do I do with it now ?
I'm using v1.0.8
FPC2.62
SVN 40573
i386-win32-win32/win64

Thank you.

[Lacak2]

dblib.dll is needed only for TMSSQLConnection
(for TODBCConnection you do not need it)
Just put this dll into your application directory.
(where is your  compiled EXE)

[Zath]

dblib.dll is needed only for TMSSQLConnection
(for TODBCConnection you do not need it)
Just put this dll into your application directory.
(where is your  compiled EXE)

Thanks but it still fails.

[BigChimp]

No idea what you mean by "it" or "fails"

http://wiki.lazarus.freepascal.org/Lazarus_Faq#What_is_the_correct_way_to_ask_questions_in_the_forum.3F

[Zath]

No idea what you mean by "it" or "fails"

http://wiki.lazarus.freepascal.org/Lazarus_Faq#What_is_the_correct_way_to_ask_questions_in_the_forum.3F

If I create a basic form with an MSSQL connection component on it, populate it's settings for the database, leave Connected as false, it compiles as a blank form. Fine.
If I then try and compile it with the MSSQL component Connection property set to true, it says it can't find the dll it needs.

Here's a screenshot.

[BigChimp]

Screenshot seems to show you're not compiling but switching on the connected property to true while in design-time.

IIRC, the dll should then be in the Lazarus directory. Another alternative is to put it in the system directory, which I do on my dev machine.

When you compile the program, once again the dll needs to be in the search path (e.g. the system directory) or the executable directory.

This applies to all dlls used with Lazarus - or at least all database drivers.

[anis2505]

Screenshot seems to show you're not compiling but switching on the connected property to true while in design-time.

IIRC, the dll should then be in the Lazarus directory. Another alternative is to put it in the system directory, which I do on my dev machine.

When you compile the program, once again the dll needs to be in the search path (e.g. the system directory) or the executable directory.

This applies to all dlls used with Lazarus - or at least all database drivers.

Hi sorry for waking this issue again from the dead BUT I have the dlls it's on my project directory side by side with the executable but no chance I did compiled lots of time but still the same error metioned by Zath

Thanks in advance

regards

[marcov]

Read the comments better. If you set the connection's enable property to true designtime, then both the Lazarus IDE and the application must find the DLL.

[anis2505]

Read the comments better. If you set the connection's enable property to true designtime, then both the Lazarus IDE and the application must fine the DLL.

Take it easy.
My problem isn't on open or closed connection my problem is the executable doesn't detect the dlls.

[Pascaluvr]

Ansi - if the connection wasn't set to Open then Laz wouldn't need to find the DLL.

On a Windows 7 system (that I am guessing you have) - place the DLL in c:\Windows\SysWOW64

[anis2505]

Hi

Now I get this error

Server name not found in configuration files
Unknown host name machine

The same configuration work fine for VS ASP.NET, Real studio, HeidiSQL and of-course SQL Server Management Studio.

So please someone provide me with an example of correct configuration.

Thanks in advance and sorry for bother and BTW again take it easy "MARCOV" .

[marcov]

Take it easy.
My problem isn't on open or closed connection my problem is the executable doesn't detect the dlls.

I suspected the Lazarus IDE might want to load the DLL at the moment a connection goes live, or if you try to edit fields (populating with schema data from the database-> connection).

What other packages do is irrelevant. Put a copy of the DLL (1) next to the application (2) next to the IDE (3) a place where both applications search.

In the case that you have mixed 32-bit/64-bit environments, please note so.

[Zath]

Just thought I'd bump this again.

The same error has appeared again after installing the latest Lazarus version.

Can't this dll be included with lazarus so it is made available when using these components ?

[goodname]

Can't this dll be included with lazarus so it is made available when using these components ?

I'm sure MS would not be happy about other projects or companies distributing their dll's. Know of a MS boot CD that had this issue and basically ended up saying go to the install CD you got with your windows operating system to get the required dll files.

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.

In the end it is MS job to provide the basic ability to connect to their product. Lazarus has provided the wrapper to be able to use that basic connection tool. If you find a problem connecting to a specific dll version then let the Lazarus project people know so they can do something about the wrapper.

[BigChimp]

Except dblib.dll is not an MS dll in this case; it can be generated by FreeTDS.

See here:
http://wiki.lazarus.freepascal.org/mssqlconn
and here for a download location:
ftp://ftp.freepascal.org/fpc/contrib/windows/