I coded an add in to be used only for 48days starting 28-Oct-04. No
before that and not after that. Just passing the instructions to use
accordingly is not sufficient. If any user uses it after that or befor
that, it will screw up the data.

How to acheive it programetically?

Thanks

--
siri
-----------------------------------------------------------------------
sirin's Profile: http://www.excelforum.com/member.php...fo&userid=1528
View this thread: http://www.excelforum.com/showthread.php?threadid=26951

You could test the date, and if not in your parameters, delete the add-in
code. See www.cpearson.com/excel/vbe.htm for the code deletion technique

--

HTH

RP

"sirin" wrote in message
...

I coded an add in to be used only for 48days starting 28-Oct-04. Not
before that and not after that. Just passing the instructions to user
accordingly is not sufficient. If any user uses it after that or before
that, it will screw up the data.

How to acheive it programetically?

Thanks.


--
sirin
------------------------------------------------------------------------
sirin's Profile:
http://www.excelforum.com/member.php...o&userid=15289
View this thread: http://www.excelforum.com/showthread...hreadid=269511

Not working outside the date range (as Bob Phillips suggested) is
acceptable behavior, but destroying user data would lead most potential
customers to look elsewere and potentially get you sued by those who
don't run.

Jerry

sirin wrote:

I coded an add in to be used only for 48days starting 28-Oct-04. Not
before that and not after that. Just passing the instructions to user
accordingly is not sufficient. If any user uses it after that or before
that, it will screw up the data.

How to acheive it programetically?

Thanks.