RE: Object Authority Issue - Sometimes

Hi Jerry

If this turns out not to be something to do with the library properties as
Rob suggested, then you might want to consider how the connection to iNav
was made. Did you connect as the same user ? Are the objects in question
created by the same user ?

Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Adams
Sent: Thursday, 28 February 2008 4:23 a.m.
To: Midrange-L
Subject: Object Authority Issue - Sometimes

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.