access violation

frank · Post by **frank** » Sun 22 May 2005 12:57

Hello,

when I set the connection property true in TSQLConnection Object, I get an error message "access violation at address 40A044A8. Read from address 40A044A8".

object TSQLConnection1: TSQLConnection
ConnectionName = SQLServerConnection
DriverName = SQLServer
GetDriverFunc = getSQLDriverSQLServer
LibraryName = dbexpsda.dll
LoadParamsOnConnect = True
Params.Strings
(
BlobSize = -1
HostName = myPC\myINSTANCENAME
DataBase = myDATABASE
DriverName = SQLServer
User_Name = sa
Password = ****
LongStrings = True
EnableBCD = True
FetchAll = True
)

I'm using C++ Builder 6.0, local MSDE Ver. MSDE2000A, Win 2000 SP4, MDAC Vers. 2.8 and dbExpress driver for SQL Server Ver. 2.50.5.

Thank's for help.
Frank

Ikar · Post by **Ikar** » Mon 23 May 2005 07:28

> when I set the connection property true in TSQLConnection Object, I get an
> error message

Do you have this error at run-time and at design-time?

> LoadParamsOnConnect = True

On using this property you also should assign values of dbxdrivers.ini and dbxconnections.ini files. Usually they are located by path c:\Program Files\Common Files\Borland Shared\DBExpress\

frank · Post by **frank** » Mon 23 May 2005 16:23

Thank's for your reply.

It's only at design-time.

Here are the values of dbxdrivers.ini
[SQLServer]
GetDriverFunc=getSQLDriverSQLServer
LibraryName=dbexpsda.dll
VendorLib=sqloledb.dll
BlobSize=-1
DataBase=myDATABASE
User_Name=sa
Password=****
HostName=myPC\myINSTANCENAME

and the values of dbxconnections.ini
[SQLServerConnection]
BlobSize=-1
DataBase=myDATABASE
DriverName=SQLServer
User_Name=sa
Password=***
HostName=myPC\myINSTANCENAME
LongStrings=True
EnableBCD=True
FetchAll=True

Ikar · Post by **Ikar** » Wed 25 May 2005 07:21

Please try to temporary set LoadParamsOnConnect to False

frank · Post by **frank** » Wed 25 May 2005 09:16

I get the same error message with LoadParamsOnConnect = False

Ikar · Post by **Ikar** » Fri 27 May 2005 12:08

Try to reproduce the problem at run-time.
Some CBuilder users have informed us once about similar problems but we couldn't reproduce them. At all known for us cases re-installing CBuilder solved the problem. Probably, it would be enough to delete a proper CBuilder path in the registry.