Hi Chris, well I am glad that my instincts have not rusted (I thought this was ot relevant). Anyhow, I am trying to see the load modules and when EG initializes what sequence etc it follows (just like what rtrace provides).
Also, this is unfair to you but have to ask if you heard about this: The option to generate pass-through SQL in EG does not generate the SQL correctly. EG does not generate the FROM clause correctly. The table owner needs to be included.
EG is a .NET application. The sequence in which DLLs (assemblies) are loaded is, well, I'm not sure why you would care to know that.
The spirit behind RTRACE for SAS was so that customers who built line-of-business SAS/AF applications could optimize their SAS installation to contain only the necessary modules. (This was back when disk space was expensive, and we shipped SAS on 3.5" floppy disks!)
EG has no such support for a "subsetted" install, so outside than our own efforts to optimize performance of the app, we don't expect customers to be concerned with the module loading.
Also, I'm talking to our query expert about the passthru issue. It's likely that the library you're using for the query has a different default schema specified than the table you're trying to use in the query. Is this DB2? A workaround would be to assign a second library that references the desired schema, and then join with the table from that second schema. If you need more details, contact SAS Technical Support.
Regarding the Pass through all permission, schema access etc and non-passthrough were examined and all works. What we have found is that when query builder despite given schema= value omits it in its generated SQL. If one corrects that generated SQL it works.
Regarding the passthru issue, the suggestion I just asked Chris to post would be the way to get it to work if you were NOT using explicit passthru. That is, having a separate library setup each of which could access the tables you want to use.
I believe if you are using passthru you would need to actually connect with the user id which is the owner or else has the correct default schema (depending on which database you are working with).
I think there should be a way for you to get it to work unless you are trying to join data from different owners/schemas. But in any case if you're unable to get your example to work by altering the login, then please contact SAS Technical Support and we'll track the issue.