Adding restrictions to database until I am paid

  • Thread starter Thread starter BBKIN
  • Start date Start date
B

BBKIN

Is it legal to put some restrictions in an Access database that will limit
functionality until a client pays his bills?

I am working on a database for a client, however every time payment is due
the guy avoids me. I have to hunt him down for every check. Recently, one of
his checks bounced and he said he would pay cash. He set up a time for
payment, and when that time came, he was not available (again).

Can I legally add some restrictions to a database that will stop it dead in
its tracks until I am paid?

What do you all do for deadbeat clients? I am not sure if he is
intentionally trying to avoid paying me, or if he is just dumb and doesn't
understand.
 
Most people have the "Turn the Key and go" mentality.
They don't have the concept of what it takes to create a DB.

More directly to your question. It is best you ask an attorney. Here is my
non-legal, opinion
1) stopping the dB from working can open you for damages suffered from
losses in his business.
2) Make the application a mde so your code is atleast protected.
3) refuse to do support until he pays his bill.
4) send him a formal letter(signature, and proof of delivery), stating that
unless payment arrangement are met, you will be forces to de-activate the
application till it is paid for.
 
Great idea about the .mde conversion. I didn't know what that was until now.
That is an excellent first step.
4) send him a formal letter(signature, and proof of delivery), stating that
unless payment arrangement are met, you will be forces to de-activate the
application till it is paid for.
Click to expand...

Sounds nice, but how would you deactivate it?
 
{Sounds nice, but how would you deactivate it?}
I thought you had that worked out when you mentioned limiting function.
There a many schemes.
Having a Key algorithm that requires the key file be in the same directory.
if it is not there then the program will not run.
Have the key rotated every month so he has to receive a new key from you to
keep it running.

have it access your website for a new key.

I thought you were sending new updates, so when you send him one, have it
timed to stop working at the end of the month.
you have to send him a new copy each month, after he as paid.
 
Seems pretty involved. I am sure I could learn a lot from those techniques,
and I'll look into them. Thanks for the info.

Alternatively, what do you think about creating and ActiveX DLL with a
password. Basically, allow them restricted access if they enter one certain
password (or no password), then if they enter another password, full access?
 
Back
Top