|
Thanks for the response. I was hopping to get more activity on this, but I guess I need to have a more popular subject. Something religious perhaps? :) The way I read the API documents, it looked like setting the Default usage limit to zero users, the Grace period to 30 days, and then set allow default usage limit grace period to Yes would do the job for me. According to the API documentation, if I allow a default grace period, then "The default usage limit is the number of users that are able to use the product or feature before the license key is installed. Thus, an unlimited number of users can use the product or feature for the number of days in the grace period without having a key." I could certainly use the product, but what confuses me is the return of the permanent expiration date (9999999). I got the same response when I set the grace period to zero days. I was not planning on explicitly issuing license requests in the applications, but was just going to check when the license expires. Like I said, I don't care how many users or what size machine. They should just have a license to run the product on a particular CPU after the trial period expires. Perhaps I can just auto-generate a temporary key at product installation time. This is an evenings and weekends project, so will try some other combinations this weekend. Thanks again for the help. At 10:51 AM 5/30/00 +1000, Lo wrote: >We developed a similar product a while ago, and if my memory does not trick >me, grace period is always related to the user limit, not to the product as >such. To make your product enter the grace period you have to request the >default number of licences + 1. Needless to say, you have to explicitely >issue licence requests from your application. Only at this point the grace >period starts. In your definition the default number of users is set to 1, >consequently, to enter the grace period you have to concurrently request at >least 2 licences. Dave Murvin DRM Enterprises, Inc. davem@drme.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.