I have searched but found nothing that helped answer my problem.
I got my dba to create a view on a SQL database which I use in designer to get around certain problems I was having creating specific objects. This worked perfectly. However when I use any object created from the view table with any in a table with and outer join on I get the following error.
[Microsoft][ODBC SQL Server Driver][SQL Server]Joined tables cannot be specified in a query containing outer join operators. View or function ‘V_Collision_Vehicle’ contains joined tables.4424
Can anyone think why this is a happening or perhaps offer me some kind of solution as I am stumped.
Just a shot in the dark…you may want to get this created as an actual table instead of a view. I think this problem is arising because of the fact that a view is ‘created’ / run on demand. There seems to be a conflict in that the tables are joined to create the view are conflicting with the outer joins on your universe when you run the query as whole…
I have a Person Table, A Vehicle Table and a Contributory Factor Table and these are all joined in a view, but are also used as tables seperately in the universe
Sorry I know very little about the database side - Is it possible for them to be joined in a table at database level then rather than just in a view? and do you think my dba will be willing to do this.
I’m assuming that Andreas is asking this because he suspects that you have outer joins in your view. I would take this assumption a step further and assume that you are using SQL Server without setting the outer join parameter in your prm file. This thread will probably help you.
I had looked at that thread earlier and you are correct in assuming that I have not altered the .prn file. This is a universe that is going to be used by many users through WebI - will altering the .prn file only work for my local full client machine?
Yes, the PRM file is machine specific. This will need to be amended on any of your servers that start an instance of the full client - either ZABO or Full client report run over infoview - for use by your users.
Fat clients need to have the amended prm file on their machine for the changes to take effect.
Finally, if you are required to run Webi instances using these settings, there a different set of prm type files to amend - the names of which escape me off the top of my head… :?