They would probably have to be able to reverse engineer your service programs if they wanted to hack it bad enough.
Just don’t advertise it as a licensing module.
But I understand your point.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>
----------------------------------------------------------------------
message: 1
date: Sat, 21 Mar 2026 03:17:20 +0000
from: Brian May <bmay@xxxxxxxxxxxxxxxxx>
subject: Re: RPG Service Program vs Include Source for Shared
Subprocedures and SQL Calls
The only time I recommend /INCLUDE is for license key/security functions in vendor software. And that only so someone can't try to bypass them.
Brian May
Profound Logic Software
Principal Technology Evangelist
http://www.profoundlogic.com<
http://www.profoundlogic.com/>
<
http://www.profoundlogic.com/>
937-439-7925 Phone
877-224-7768 Toll Free
[Profound Logic Logo]
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.