Subject | Re: [firebird-support] more licensing API blues |
---|---|
Author | Helen Borrie |
Post date | 2004-11-15T14:55:53Z |
At 12:00 PM 15/11/2004 +0000, you wrote:
guess I'm curious why you're not just using the TIBLicensingSevice
component. This is all it takes (from the help in the DevGuide):
<<
Adding a software activation certificate
Use the AddLicense method along with the Key and ID properties to add a
software activation certificate. For example, the following code attaches
to a server, and adds a license with the click of a button after the Key
and ID are entered into Edit components.
procedure TForm1.Button1Click(Sender:TObject);
begin
with IBLicensingService1 do
begin
ServerName :='Poulet';
LoginPrompt :=False;
Protocol :=Local;
Params.Add('user_name=SYSDBA');
Params.Add('password=masterkey');
Active :=True;
try
Key :=Edit1.Text;
ID :=Edit2.Text;
AddLicense;
ServiceStart;
finally
if Active then
Active :=False;
end;
end;
end;
Using the Action property
Instead of using the AddLicense or RemoveLicense methods, you could use the
Action property:
Action :=LicenseAdd;
or
Action :=LicenseRemove;
./hb
>Hi,Firebird doesn't DO licensing and doesn't even have the Licensing API. I
>I wonder if anyone can help. I'm trying to use the InterBase
>licensing API from within a Delphi application, and thought I had it
>working but am getting strange things happening to my application
>after calling the functions (variables being reset, AVs etc.).
guess I'm curious why you're not just using the TIBLicensingSevice
component. This is all it takes (from the help in the DevGuide):
<<
Adding a software activation certificate
Use the AddLicense method along with the Key and ID properties to add a
software activation certificate. For example, the following code attaches
to a server, and adds a license with the click of a button after the Key
and ID are entered into Edit components.
procedure TForm1.Button1Click(Sender:TObject);
begin
with IBLicensingService1 do
begin
ServerName :='Poulet';
LoginPrompt :=False;
Protocol :=Local;
Params.Add('user_name=SYSDBA');
Params.Add('password=masterkey');
Active :=True;
try
Key :=Edit1.Text;
ID :=Edit2.Text;
AddLicense;
ServiceStart;
finally
if Active then
Active :=False;
end;
end;
end;
Using the Action property
Instead of using the AddLicense or RemoveLicense methods, you could use the
Action property:
Action :=LicenseAdd;
or
Action :=LicenseRemove;
>>Have you tried the Borland newsgroups?
./hb