×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I saw that a vendor package we had on our system for testing had created an SQL ALIAS for each source member within a source file.
I'm assuming this helps them do SQL analysis on a source member as well as access the last changed time info via an SQL query against SYSTABLES
Looks like an interesting technique.
However, is that the best way of determining if a member has had activity or changes or is there a better way such as running DSPOBJD against each library source file ?
SYSTABLES seems cool because a single SQL statement can get me access to all changed source members if they are ALIASed.
I would be interested to hear thoughts on whether this is a good technique for accessing system-wide source member change info.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
This mailing list archive is Copyright 1997-2024 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.
midrange.com
