BorlandTalk.com

Keith G Hicks · Guest

I know how to do this in code but how do you do it in the properties of an
actual object on a form? I've tried everythign I can think of and it won't
work. I need a connection to connect during design in order to get at
backend things. I was using the default MS SQL port of 1433 and it always
worked without any intervention on my part but recently changed to a
different port # and now I can't connect. Like I said, I can do it in code
when my app starts up by including "Data Source = <server name>,<port #>"
but that doesn't work in the actuall connection object.

Thanks in advance,

Keith

Keith G Hicks · Guest

Correct. It doesn't work. I can set up a connection string in code and it
works fine but if I enter it into the ConnectionString property of the
TAdoConnection object it doesn't work. Odd huh? Doesn't make much sense to
me. I have 2 connection objects on my data form. One is for run time and
the other is for design time. I set the connection string for the one used
at run time in code because it gets some info from the registry. It works
perfectly well including the port setting. The one I use during design time
is identical in every way except for the name of course. That's the one I'm
having trouble with. Like I said it doesn't really make any sense. My
connection string is simply like this:

Provider=SQLOLEDB.1;Password=<password>;Persist Security Info=True;User
ID=<user name>;Initial Catalog=<db name>;Data Source=<server name>,<port#>

"Brian Bushay TeamB" <BBushay (AT) Nmpls (DOT) com> wrote

Keith G Hicks · Guest

Something even stranger. My brother (who's working with me on the same
project) couldn't get any of the stuff below to work so he tried "Data
Source = <server name>; Port = <Port #>" and it works for him. He found this
in a MySql webpage somewhere. We're both running MS SQL 2000 and not MySql.
What he's doing doesn't work at all on my machine. I'm clueless as to why it
would work on his. I'm wondering if this is some weird MDAC issue. I'm going
to check with him to see what version he has. I'm sure it's recent since
he's running Windows XP and has updated his SQL installation. I can't
beleive that would make a difference though.

"Keith G Hicks" <krh (AT) comcast (DOT) net> wrote

Correct. It doesn't work. I can set up a connection string in code and it
works fine but if I enter it into the ConnectionString property of the
TAdoConnection object it doesn't work. Odd huh? Doesn't make much sense to
me. I have 2 connection objects on my data form. One is for run time and
the other is for design time. I set the connection string for the one used
at run time in code because it gets some info from the registry. It works
perfectly well including the port setting. The one I use during design time
is identical in every way except for the name of course. That's the one I'm
having trouble with. Like I said it doesn't really make any sense. My
connection string is simply like this:

Provider=SQLOLEDB.1;Password=<password>;Persist Security Info=True;User
ID=<user name>;Initial Catalog=<db name>;Data Source=<server name>,<port#>

"Brian Bushay TeamB" <BBushay (AT) Nmpls (DOT) com> wrote

Keith G Hicks · Guest

Well I spoke too soon. His method does work in code but not in the
ConnectionString property in the object inspector. This is becoming very
frustrating. Here's our code for setting up the connection on application
startup:

sDbConnStr := 'Provider=SQLOLEDB.1;Password=' + sDbPwd + ';'
+ 'Persist Security Info=True;User ID=' + sDbUsrName + ';'
+ 'Initial Catalog=CustDB;Data Source=' + sDbSrvName + ';Port=' +
sSqlPortNum;

cnnCon.ConnectionString := sDbConnStr;
try
cnnCon.Connected := true;
except
Windows.MessageBox(Application.Handle, 'Database connection failed.',
PChar(oInternalSysInfo.CoDBAName), MB_ICONINFORMATION or MB_OK);
Application.Terminate;
end;

The above works fine. If I set a break point and get the value of
"sDbConnStr" and then paste that into the ConnectionString property of the
object (without the quote marks of course) I get "Invalid connection string
attribute" as I'd expect.

If I change the code above to:

... + 'Initial Catalog=CustDB;Data Source=' + sDbSrvName + ',' +
sSqlPortNum;

it also works fine from code but NOT from the ConnectionString property in
the object inspector (I can paste it in there but when I try to set the
Connected property to true I get an error that it can't find the db.

Why would I get different behavior in code then I get in the object
inspector at design time?????

"Keith G Hicks" <krh (AT) comcast (DOT) net> wrote

Something even stranger. My brother (who's working with me on the same
project) couldn't get any of the stuff below to work so he tried "Data
Source = <server name>; Port = <Port #>" and it works for him. He found this
in a MySql webpage somewhere. We're both running MS SQL 2000 and not MySql.
What he's doing doesn't work at all on my machine. I'm clueless as to why it
would work on his. I'm wondering if this is some weird MDAC issue. I'm going
to check with him to see what version he has. I'm sure it's recent since
he's running Windows XP and has updated his SQL installation. I can't
beleive that would make a difference though.

"Keith G Hicks" <krh (AT) comcast (DOT) net> wrote

Correct. It doesn't work. I can set up a connection string in code and it
works fine but if I enter it into the ConnectionString property of the
TAdoConnection object it doesn't work. Odd huh? Doesn't make much sense to
me. I have 2 connection objects on my data form. One is for run time and
the other is for design time. I set the connection string for the one used
at run time in code because it gets some info from the registry. It works
perfectly well including the port setting. The one I use during design time
is identical in every way except for the name of course. That's the one I'm
having trouble with. Like I said it doesn't really make any sense. My
connection string is simply like this:

Provider=SQLOLEDB.1;Password=<password>;Persist Security Info=True;User
ID=<user name>;Initial Catalog=<db name>;Data Source=<server name>,<port#>

Keith G Hicks · Guest

Keith G Hicks · Guest

I also created an ODBC datasource and used it to access my SQL tables from
an Access 2000 mdb. It works just fine too. But if I use that same ODBC
datasource in a TAdoConnection using the ODBC settigns it doesn't work at
all. It fails.

keith

"Keith G Hicks" <krh (AT) comcast (DOT) net> wrote

Keith G Hicks · Guest

"Brian Bushay TeamB" <BBushay (AT) Nmpls (DOT) com> wrote

Keith G Hicks · Guest

Well I just tried all this on my laptop which is running MDAC 2.7 and it all
works fine. I can create and connect with TadoConnection in design. What
version of MDAC are you running? I wonder if D7.1 has a problem with MDAC
2.81 because that's all I'm left with considering now. And with all the
nightmares MDAC can cause I'm not really considering reverting to an earlier
version on my main PC. The idea of doing that sort of scares me. -keith

Gert de Boom · Guest