Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
How to disable PB Catalog tables for OLE-DB connections?
242 views
Skip to first unread message
Steve
Jul 28, 2008, 9:52:17 AM7/28/08
to
Does anyone know how to tell PowerBuilder 10.5.2 to NOT try
and create the PB Catalog tables every time it connects to
an OLE-DB database? With the ODBC interface, it is
accomplished by adding the following line to the
PBODB105.INI file:
PBNoCatalog='YES'
I tried creating a file named PBOLE105.INI with a similar
entry for the OLE-DB interface, but that didn't work.
I don't know why this behavior was EVER programmed into
PowerBuilder. It is RARELY ever the case in an enterprise
development environment that the developers are actually
given the authority to create any tables at all. The DBA's
are the only one with the keys to the kingdom.
There surely is a way to disable this. Anyone know how?
and create the PB Catalog tables every time it connects to
an OLE-DB database? With the ODBC interface, it is
accomplished by adding the following line to the
PBODB105.INI file:
PBNoCatalog='YES'
I tried creating a file named PBOLE105.INI with a similar
entry for the OLE-DB interface, but that didn't work.
I don't know why this behavior was EVER programmed into
PowerBuilder. It is RARELY ever the case in an enterprise
development environment that the developers are actually
given the authority to create any tables at all. The DBA's
are the only one with the keys to the kingdom.
There surely is a way to disable this. Anyone know how?
Steve
Jul 28, 2008, 10:49:50 AM7/28/08
to
This worked PERFECTLY !
Oddly enough, from the factory install, the PB.INI file
already contained an entry in the [Database] section that
read NoCatalog=No. I first tried changing it to
NoCatalog=Yes, in keeping with the use of Yes or No instead
of 0 or 1, but that did NOT work. As soon as I changed it to
the value 1 instead, that worked. Thanks sooooooo much!
=Steve=
> Unless I'm missing something, you can do this with the
> following INI setting:
>
> [Database]
> NoCatalog=1
>
> Or you can go to the Database painter, Design menu,
> Options item, General tab and uncheck "Use Extended
> Attributes".
>
> Ken
>
> <Steve> wrote in message
> > news:488dd8ad.7ac...@sybase.com... Hi Paul-
> > I do not have the PB Cat tables created under a
> > different user ID, nor do I want to have to go to the
> > DBA's and ask them to create these tables. It is strange
> > how there is a mechanism to disable the use of these
> > catalog tables under ODBC, but not under any other
> > database interface. Every time I connect to the OLE-DB
> > database (Db2), I get the nuisance error message [The
> > current provider does not support the ITableDefinition
> > interface]. Very annoying.
> =Steve= >
> >> If you've got the PB Catalog tables created under a
> >> different user schema, you can tell PB to look there
> for >> them.
> >>
> >> On the System tab in the connection profile, add the
> >> schema owner account to the "PowerBuilder Catalog
> Table >> Owner" field. That will stop PB from trying to
> create them >> under the developers' individual accounts.
> >>
> >> I'm not sure how to totally disable the Catalog table
> >> checking with OLE-DB...
> >>
> >> Paul Horan[TeamSybase]
> >>
> >> <Steve> wrote in message
> >> > news:488dcf11.794...@sybase.com... Does
Oddly enough, from the factory install, the PB.INI file
already contained an entry in the [Database] section that
read NoCatalog=No. I first tried changing it to
NoCatalog=Yes, in keeping with the use of Yes or No instead
of 0 or 1, but that did NOT work. As soon as I changed it to
the value 1 instead, that worked. Thanks sooooooo much!
=Steve=
> Unless I'm missing something, you can do this with the
> following INI setting:
>
> [Database]
> NoCatalog=1
>
> Or you can go to the Database painter, Design menu,
> Options item, General tab and uncheck "Use Extended
> Attributes".
>
> Ken
>
> <Steve> wrote in message
> > news:488dd8ad.7ac...@sybase.com... Hi Paul-
> > I do not have the PB Cat tables created under a
> > different user ID, nor do I want to have to go to the
> > DBA's and ask them to create these tables. It is strange
> > how there is a mechanism to disable the use of these
> > catalog tables under ODBC, but not under any other
> > database interface. Every time I connect to the OLE-DB
> > database (Db2), I get the nuisance error message [The
> > current provider does not support the ITableDefinition
> > interface]. Very annoying.
> =Steve= >
> >> If you've got the PB Catalog tables created under a
> >> different user schema, you can tell PB to look there
> for >> them.
> >>
> >> On the System tab in the connection profile, add the
> >> schema owner account to the "PowerBuilder Catalog
> Table >> Owner" field. That will stop PB from trying to
> create them >> under the developers' individual accounts.
> >>
> >> I'm not sure how to totally disable the Catalog table
> >> checking with OLE-DB...
> >>
> >> Paul Horan[TeamSybase]
> >>
> >> <Steve> wrote in message
> >> > news:488dcf11.794...@sybase.com... Does
Ken Balakrishnan
Jul 28, 2008, 10:45:00 AM7/28/08
to
> the following INI setting
The PB.INI file, that is.
Ken
"Ken Balakrishnan" <kNOe...@cpsREMOVEME92.com> wrote in message
news:488ddaed$1@forums-1-dub...
Ken Balakrishnan
Jul 28, 2008, 10:42:53 AM7/28/08
to
Steve
Jul 28, 2008, 10:33:17 AM7/28/08
to
Paul Horan[TeamSybase]
Jul 28, 2008, 10:27:59 AM7/28/08
to
If you've got the PB Catalog tables created under a different user schema,
you can tell PB to look there for them.
you can tell PB to look there for them.
On the System tab in the connection profile, add the schema owner account to
the "PowerBuilder Catalog Table Owner" field.
That will stop PB from trying to create them under the developers'
individual accounts.
I'm not sure how to totally disable the Catalog table checking with
OLE-DB...
Paul Horan[TeamSybase]
<Steve> wrote in message news:488dcf11.794...@sybase.com...
0 new messages