Unable to write from a Daemon to MsSQLServer

[Dunsany]

Hi,

I wrote a server application (with Delphi6) few month ago. When i decided to turn it into an Application Service, there were no trouble at all, except one: it doesn't write on MsSQLServer 2000. I Changed security properties (Windows & SQL Server) on my SQL server. My connection string is good (with the Password and so on). At design time, the build connection test works, but not at running time. I use ADO Components (connection & query).
If someone tried to write with a daemon & ADO component on MSSQLServer2k or have an idea...
(excuse my english, i'm french..

best regards

 

[whosrdaddy]

Hi,

you must call Coinitialize() (put ActiveX unit in uses list) before activating ADO components and Couninitialize() at service destruction.

--------------------------------------
What You See Is What You Get

 

[Dunsany]

I've got an 'Undeclared Identifier', which Library use CoInitialize() ?

 

[whosrdaddy]

activeX unit (like I said)...

--------------------------------------
What You See Is What You Get

 

[Dunsany]

Sorry, i read too fast... But it still doesn't work.

 

[whosrdaddy]

then you'll have to show some code, maybe we can help

--------------------------------------
What You See Is What You Get

 

[Dunsany]

Query is simple as that (it's a test with Ms Northwind DB):

var
RegionID: integer;
RegionDescription: string;
begin
RegionID:=5;
RegionDescription:='Green grass & pretty girls !';

With ADOQuery2 do
begin
SQL.Clear;
SQL.Add('SELECT * FROM Region');
Active:= True;

Insert;
FieldByName('RegionID').Value:=RegionID;
FieldByName('RegionDescription').Value:=RegionDescription;
Post;
end;

ps: it's an SQLServer access to DB so Connection string has a Password. Connection works with the Query Analyser and at design time.
This code works with an executable application. So where is the bug ?

 

[whosrdaddy]

I don't believe the problems lies into your query.

show me the service initialization part , I mean the part were the service thread is created an where you set the ADOconnection.active property to true...

--------------------------------------
What You See Is What You Get

 

[Dunsany]

I maked it fast. So there is just a TADOQuery component with the connection string, and your CoInitialize(nil) in ServiceCreate with a call to a timer. The OnTime procedure (of the timer) is writing the DB with the query. And of course a CoUnInitialize() in ServiceDestroy. Nothing else to declare...