Board index » delphi » MSSQL "Grant" Problem - Quick Reports

MSSQL "Grant" Problem - Quick Reports

Application runs fine in all respects except Quick Reports:  Added a QRep that uses a TStoredProc dataset.  The TQuery simply seledcts a group of fields  and then does an order by on some of them.  Nothing unusual that I can see.  When myRpt.preview or print is called, I get the ODBC error: "GRANTOR does not have GRANT permission."
Using MSSQL 2000, NT4 server, Delphi 5.  Permissions are granted by MSSQL role and when logged in users are members of that role.  Nothing diff. between this TStoredProc and all the others in the app., including GRANT EXECUTE languange, etc.  Can't figure out what's happening here.  

 

Re:MSSQL "Grant" Problem - Quick Reports


Quote
"Paul S." <kr...@xmission.com> wrote in message news:3b5721ef$1_1@dnews...

> Application runs fine in all respects except Quick Reports:  Added a QRep

that uses a TStoredProc dataset.  The TQuery simply seledcts a group of
fields  and then does an order by on some of them.  Nothing unusual that I
can see.  When myRpt.preview or print is called, I get the ODBC error:
"GRANTOR does not have GRANT permission."
Quote
> Using MSSQL 2000, NT4 server, Delphi 5.  Permissions are granted by MSSQL

role and when logged in users are members of that role.  Nothing diff.
between this TStoredProc and all the others in the app., including GRANT
EXECUTE languange, etc.  Can't figure out what's happening here.

I have no clue either (sorry). Just wanted to share my own tears with you. I
had stored procedures that worked normally for months. All of the sudden,
and I really mean this - sudden, without any forewarning or any code
changed, they would stop working. No matter what I'd do, I'd get no
(expected) results out. With one procedure, I went as far as to comment out
all the code, and keep one line that sets an absolute value to output var
(set @myOutVar = 15). Have I seen 15 coming back - NO WAY. And I tried on
different OSs, and different machines - nada. Translated the call to ADO -
and it works like a Swiss clock.

Now, your problem may have nothing to do with the fact that you're using BDE
with MSSQL 2000, but you should definitely consider switching to ADO. The
sooner the better.

Bonne chance.

rb

Other Threads