[AccessD] The Polyp Problem

Nicholson, Karen cyx5 at cdc.gov
Thu Jan 20 10:33:16 CST 2005

That sounds interesting.  But what if they do pay?  I just want to
torture those clients who think of us as prostitudes to be used when
needed, and after they get what they want, and you never hear from them
again.  How can I treat those with respect that deserve it?  Does this
encrypted date require you to keep sending them updated .mde's?

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
- Beach Access Software
Sent: Thursday, January 20, 2005 11:17 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] The Polyp Problem


If you're delivering an mde it's a snap.  Just put a date check in the 
opening form open event and quit the program if the date is past.  I
put a 'date last accessed in a table and check to see if today's date is

less than the date last accessed.  That's so that they don't just move
clock back to a date prior to the date bomb.

In my commercial product I have a key with an encrypted expiration date 
which the user has to get updated every so often.  That way I don't have
worry about illegal copies being made.  I can send out an evaluator with
30 or 60 day expiration.  Bu that's probably more elaborate than you

Rocky Smolin
Beach Access Software

----- Original Message ----- 
From: "Nicholson, Karen" <cyx5 at cdc.gov>
To: <accessd at databaseadvisors.com>
Sent: Thursday, January 20, 2005 5:10 AM
Subject: [AccessD] The Polyp Problem

I know this has been discussed before, but I sort of removed a polyp
from my client abuser list last night, as a woman has the right to flip
out on deadbeats.  That is the law.  Here is the story.  Client
contracts for a job; agrees to pay whatever way - some do in stage I,
more in stage II and the rest in stage III.  It is clearly stated that
changes to the requirements of the system will be discussed and
additional invoicing will be required.  Polyp continuously *forgets* to
pay invoices as that is not is department, makes wild changes to the
system - "Oh, didn't I tell you?  Truck A, B or C can not go on streets
with a 2 Ton Limit?  You can just program that in, right?"  Or emergency
call - finger nail bimbo's system won't work and it is the hub.  Your
system broke it, we can't function, come over here right now.  Drop
everything, run over, and low and behold the cable is unplugged.  Three
hours out of your day, gee thanks.  Oh, we can't pay you, it has been a
bad year.  And that $2000 we still owe you from August?  That is coming
soon.  Hello, it is snowing!

In my warped world, I would like to put code in the program that when a
payment is not received, the system stops working.  When the bill is
paid, the user can have the encrypted password to keep working.

Doesn't that sound easy?  One final password when the system is paid in
full.  I know a geek could break into it and get around the password,
but these people are cheap to begin with if they won't pay and not work
continuing working for anyway.  Ideas?

AccessD mailing list
AccessD at databaseadvisors.com
Website: http://www.databaseadvisors.com

AccessD mailing list
AccessD at databaseadvisors.com
Website: http://www.databaseadvisors.com

More information about the AccessD mailing list