Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

ini parameter to not identify table owner explicitly

2 posts in PB Infomaker Report Writer Last posting was on 1997-09-05 18:59:52.0Z
clarcher Posted on 1997-09-05 15:16:31.0Z
Newsgroups: sybase.public.infomaker.general
From: "clarcher" <clarcher@gte.net>
Subject: ini parameter to not identify table owner explicitly
X-Newsreader: Microsoft Internet News 4.70.1161
Date: Fri, 05 Sep 1997 11:16:31 -0400
Lines: 9
Message-ID: <348_01bcba17$8d3c1370$249473cf@clarcher>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.infomaker.general:7467
Article PK: 244522

Deploying reporting application with ODBC to MS SQL SERVER 6.5. Many
reports use views (granted select privilege to public) created by different
user id than those running report(s). Reports refer only to table name -
but application gives error that table-name is invalid object. Is there a
dbparm I can use to suppress this?

Chet Archer


Terry Dykstra Posted on 1997-09-05 18:59:52.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: ini parameter to not identify table owner explicitly
X-Newsreader: Microsoft Internet News 4.70.1161
Date: Fri, 05 Sep 1997 14:59:52 -0400
Lines: 23
Message-ID: <348_01bcba36$2802be40$8366e4cf@tdykstra.cfol.ab.ca>
References: <348_01bcba17$8d3c1370$249473cf@clarcher>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.infomaker.general:7465
Article PK: 244521

I am confused. First you state that "many reports use views" and then you
state that "reports refer only to table name".

I am not a SQL Server user, but I would think that you need to give select
privileges to the underlying tables. Giving public select privileges to
views doesn't do much good if you don't have select privileges on the
tables within the views (unless SQL Server works differently from Oracle)

Terry Dykstra (TeamPS)

clarcher <clarcher@gte.net> wrote in article
<01bcba17$8d3c1370$249473cf@clarcher>...
> Deploying reporting application with ODBC to MS SQL SERVER 6.5. Many
> reports use views (granted select privilege to public) created by
different
> user id than those running report(s). Reports refer only to table name -
> but application gives error that table-name is invalid object. Is there a
> dbparm I can use to suppress this?