Crystal Reports Temp tables - Driving Me crazy

Question

Our ongoing saga with temp tables and crystal reports continues. I am ready to go crazy, so any help would be appreciated.
Notes:
I create the ##tempsmall table in query analyzer, so it is present when the code executes.
When I use the sa/Corinne credentials, it works.
When I use a non sa set of credentials, I get an error saying the temp table is not found.
When I add the non sa user to the tempdb as a user, with DBO permissions, It works.
Code is below
Dim Report As New ReportDocument()
Report.Load("C:\KI\Customers\Live Customers\Brookledge\ReportRD\CrystalReportsApplication1\Projects.rpt")
Dim LogInfo As New TableLogOnInfo
Dim Tbl As Table
For Each Tbl In Report.Database.Tables
  LogInfo = Tbl.LogOnInfo
  LogInfo.ConnectionInfo.ServerName = "ocamb-vista"
  LogInfo.ConnectionInfo.DatabaseName = "mapps20"
  ' We need to figure out how to make this work with a non sa user?
  LogInfo.ConnectionInfo.UserID = "medequipuser"
  LogInfo.ConnectionInfo.Password = "mapps"
  'LogInfo.ConnectionInfo.UserID = "sa"
  'LogInfo.ConnectionInfo.Password = "corinne"
  Tbl.ApplyLogOnInfo(LogInfo)
Next Tbl
Report.Database.Tables.Item(0).Location = "tempdb.dbo.##tempsmall"
Dim v As New Viewer
v.CrystalReportViewer1.ReportSource = Report
v.Show()

Answer 1

Hi Scott,
The problem is tempdb is only accessible by the Administrator account and they are typically not to be used by anyone other than the system. This is how SQL server works, any query being run will create a temp table for the DB server to use and pass that data to the calling query, once completed the tempdb is deleted.
As you have seen, unless you set permissions each time for a specific user you don't have access to it. One option is to use real tables that you can populate and delete the rows of data each time. Not very efficient though.
Crystal respects all DB permissions so it's not a CR issue.
One possibility is in your front end you could use MS SQL Server API's, if there are any, or use a stored procedure to set permissions to the temp table before calling CR to set location. Sorry no samples to do this, its a DB server question.
Another option is to write the data into a Data Set and then set the location to the DS for CR to use. If you have more than 5000 row though don't do this or your reports will have performance problems.
CR does not have any API's that will allow you to access a table that it does not have permissions to get to. Basic DB security, you'll get the same log on error trying to connect ot any table that user doens't have access to.
Thank you
Don