×
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 create any new tables in our applications by using SQL's DDL.
Actually I do it through iNav's Database...Schema tree for what it's worth.
Usually these tables come out with *Public = *All. Occasionally, they
arrive with *Public = Exclude. Why?
Potentially more info: I use iNav's "Generate SQL" function to save the
DDL to a source physical file. Sometimes I will use the RUNSQLSTM
command against said source member to create a table. Don't know if
that makes a difference. However, I just did that for a table in one of
my project libraries that had *Public = Exclude, and the table, after
"re-compiling," had *Public = All. I tried various options on the
RUNSQLSTM but it still came out as *Public = All. How it got to *Public
= Exclude is a mystery - to me, anyway.
Thanks.
As an Amazon Associate we earn from qualifying purchases.
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
