DLL errors fixed in previous commit belong to a place after connection has been established. Reporter of issue #2741 says connection does not even work with r4063.

This commit is contained in:
Ansgar Becker
2012-02-26 09:56:27 +00:00
parent bfb2c57c3a
commit 3da79f5b2b

View File

@@ -1032,13 +1032,6 @@ begin
;
if Parameters.WindowsAuth then
FAdoHandle.ConnectionString := FAdoHandle.ConnectionString + 'Integrated Security=SSPI;';
try
// Show up dynamic connection properties, probably useful for debugging
for i:=0 to FAdoHandle.Properties.Count-1 do
Log(lcDebug, 'OLE DB property "'+FAdoHandle.Properties[i].Name+'": '+String(FAdoHandle.Properties[i].Value));
except
// Silence DLL errors, see issue #2741.
end;
try
FAdoHandle.Connected := True;
FConnectionStarted := GetTickCount div 1000;
@@ -1067,6 +1060,11 @@ begin
FServerVersionUntouched := rx.Match[1];
rx.Free;
FRealHostname := Parameters.Hostname;
// Show up dynamic connection properties, probably useful for debugging
for i:=0 to FAdoHandle.Properties.Count-1 do
Log(lcDebug, 'OLE DB property "'+FAdoHandle.Properties[i].Name+'": '+String(FAdoHandle.Properties[i].Value));
DoAfterConnect;
// Reopen closed datasets after reconnecting