Re: [sqr-users] Copy-Protecting SQRs

[Tcscad@aol.com]

I am in the same boat as you are.    Have developed highly production SQR 
tools but not able to protect them.     I have created an installer program 
that 
will install SQT files using the current version of SQR available on the 
machine without showing the SQR to the user.

Even though many big companies use SQR they can easily copy and modify the 
SQRs without paying any licensing fees.      They can just copy the procedures 
and rewrite the SQR.

Gopal.


In a message dated 6/11/03 9:48:20 AM Central Daylight Time, erice@ontko.com 
writes:


> Eric,
> 
> What kind of copying are your worried about?  If it is "person A puts it on 
> a shared drive for others in the company", license it to a company or 
> department at a time.  If it is "person A posts it on the Internet", 
> monitor Google periodically.
> 
> You might want to bury some identifying code in the program somewhere so 
> that you could track the copying back to its source.  Of course anyone 
> could change it, if they knew what and where it was.
> 
> If your programs are PeopleSoft specific, I wouldn't worry too much about 
> it.  The companies that buy PeopleSoft are huge.  Why would they open 
> themselves up to a lawsuit instead of paying your license fee?
> 
> Eric
> 
> EricRection@aol.com wrote:
> > Comrades,
> > 
> > I've written a couple of SQRs I'd like to sell. PeopleSoft wasn't 
> interested, 
> > - the fools! -  even though one of the SQRs displays trees graphically, 
> which 
> > PeopleSoft hasn't been able to do (thus spake PeopleBooks: a "future 
> version" 
> > has an nVision report to print one just branch of a tree, otherwise you 
> have 
> > to use third-party software). I admit I got used to thinking of PeopleSoft 
> as 
> > The Enemty a while ago, so I'd like to market the SQRs either myself or 
> > through a conslutancy.
> > 
> > The problem is protecting the SQRs against copying. I thought of doing an 
> SQT 
> > with PSOPTIONS.LICENSE_CODE hard-coded. But SQTs don't work at all on my 
> > version of PeopleTools, per issue 717841 on Customer Connection. Worse, 
> one of the 
> > SQRs is intended to be a nightly process, and SQTs don't work through 
> Process 
> > Scheduler on v8. And to top it off, the SQT is unlikely to work on a 
> version 
> > of SQR other than that on which it was compiled. - one SQRUG posting says 
> it 
> > definitely won't work, and another from Mistah Ontko hisself says it 
> 'should' 
> > work but to expect problems.
> > 
> > So I was wondering if there was some other method to safeguard the fruits 
> of 
> > my grey matter. Ideas, anyone?
> > 
> > _______________________________________________
> > sqr-users mailing list
> > sqr-users@sqrug.org
> > http://www.sqrug.org/mailman/listinfo/sqr-users
> > 
> > 
> 
> 
> _______________________________________________
> sqr-users mailing list
> sqr-users@sqrug.org
> http://www.sqrug.org/mailman/listinfo/sqr-users
> 

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users