by Jason A. Dexte » Wed, 08 Jan 1997 04:00:00
I would like my application to expire (rendered useless)after 30 days.
After 30 days, I would like it to require a password(or registration
number) to work again. This would be for distribution/registration
purposes. Could someone suggest the best way to do something like this?
Any code examples or ideas would be greatly appreciated. Thanks
by Craig Wilso » Sun, 12 Jan 1997 04:00:00
Add the following Sub to your project
Sub TestForExpired()
Const ExpireDate = "01/02/97"
If Date > DateValue(ExpireDate) Then
MsgBox "This application has expired. Please contact ...", 16, "Expired
Application"
End
End If
End Sub
Call this procedure from your startup routine or from the Form_Load
procedure of your startup form. It will compare todays date with the
constant ExpireDate.
Craig
Quote:> I would like my application to expire (rendered useless)after 30 days.
> After 30 days, I would like it to require a password(or registration
> number) to work again. This would be for distribution/registration
> purposes. Could someone suggest the best way to do something like this?
> Any code examples or ideas would be greatly appreciated. Thanks
1. Subscription Expires when set to not Expire
Could anyone shed more light on expiring subscriptions in
SQL Server 7.0, with SP2, when the subscriptions are set
to not expire?
My publication is setup so that the subscription won't
expire. However, after 4 days of intermittent connection
to the subscriber due to a choked network, the
subscription fails with the message:
The subscription has expired and must be reinitialized at
the publisher.
I find that re-initializing all subscriptions and
snapshotting does fix the problem, but I would like to
prevent the subscription needing to be re-initialized.
Thanks for any help,
Carla.
2. Question about snapshot in Transactional replication
3. APPLICATION DEVELOPER/ Intranet Applications, Extranet applications- WA
4. ntext, nvarchar, varchar searches
5. SDK SP's
6. SQL 2000