RE: [AccessDevelopers] Self Protection

Sun, 07 Aug 2005 19:07:55 -0700

I agree - once you give it to them, it's theirs, for all practical purposes.  If you're worried about non-payment, hold onto the source until paid.  If they really need the source now, they'll pay for it now. 
 

Tom Oakes
Personal PC Consultants, Inc.
[EMAIL PROTECTED]
503.230.0911 (O)
402.968.6946 (C)
734.264.0911 (F)



From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of AAP
Sent: Sunday, August 07, 2005 7:11 AM
To: [email protected]
Subject: RE: [AccessDevelopers] Self Protection

Let them have the Source code after the final payment and not before. Leaving the lock in tact to prevent tampering and insure this is stated in the sales/purchase contract.

 

Carl

 

From: [email protected] [mailto:[email protected]] On Behalf Of George Oro
Sent: Sunday, August 07, 2005 2:29 AM
To: YG Access Dev
Subject: [AccessDevelopers] Self Protection

 

From my knowledge I know this is not possible and maybe this may sound unfair but I have to do it for my protection.

 

I have a client wants to purchase 1 of my software plus the source code therefore everything will be open to them. I have 1 module that will trigger once he reach the targeted date and the program will automatically exit. How can I avoid them to modify this code?

 

My idea at the moment is to make a .dll but they can just simply remove the code and reference not unless some of the functionality will be on that .dll too so they will be forced to used it and every end of the code, it will check the trigger date too. That make sense?

 

The main reason is the payment, it is 6 installment. I hope you understand me guys.

 

Any input will be greatly appreciated.

 

 

TIA,

George





Please zip all files prior to uploading to Files section.


YAHOO! GROUPS LINKS



Reply via email to