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


Reply via email to