Kenny, All of my clients are remote so after I make major changes to my applications I run a routine that sequences through the SYS_TABLES and assigns all tables to public. I have been stung more than once with clients calling after I installed an update saying that they were getting table access errors. John
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kenny Camp Sent: Monday, July 19, 2010 3:38 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Fiqured out what I did wrong RE: [RBASE-L] - RE: Sub report requires DB owner password? Figured out what I did wrong. After I granted CREATE privileges to PUBLIC, I changed to user PUBLIC and was able to create views and all privileges were automatically created on the view for user PUBLIC. The report designer requires the DB owner password. So I entered it and created my report and then realized I needed to add a where clause to the view I had made. So I popped out to the R> and made a new view. Because I was now OWNER again, the privileges did not automatically get assigned to the view as they did when I was PUBLIC with the CREATE privilege. Once I granted privileges to the view for user PUBLIC, the report then works as expected. I must be much more careful now that I have a DB owner defined. Kenny -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kenny Camp Sent: Friday, July 09, 2010 11:38 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Sub report requires DB owner password? I found a way to trigger an error - 2039 Unauthorized access to the table cursor1 for user public. Kenny -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kenny Camp Sent: Friday, July 09, 2010 11:34 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Sub report requires DB owner password? V7.6 I recently added a DB owner password in order to change null settings for "Public" users without affecting other users. This is working as expected but a new problem appeared that I don't understand. I wrote a simple report with a simple sub report that works great as long as you are the owner of the database. When I went live with it, it did not work and bailed out of the eep at the print statement without executing the rest of the code in the eep. Trace did not show an error and worked as expected and I was baffled at what was wrong until I realized that I had to be the owner to create the report, and I when live I was running the report as a user "Public". Tracing the report while Public did not show an error and bailed out of the eep without executing the next line of code. Maybe sub reports require DB owner if defined? Or maybe I am missing something? Or maybe my experience will help someone else troubleshoot a similar problem quicker that I resolved it. Kenny Detail line: Part_number Reserved_total_qty_var Applied_total_Qty_var Sub-report Detail line: Trace# Qty Sub-Report Footer: ------ Total
