![]() ![]() Instead it passes the correct syntax to SQL, and SQL executes normally. However, when we tell c# that we are running the report against the server/database combination specified within the Crystal report, even through we still loop through the tables to "change" the LogOnInfo, in this case Crystal doesn't loose the schema information. It's understandable why SQL Server would return the error since it can't execute the select statement because of the missing schema names. ![]() "Failed to retrieve data from the database. Because of this, SQL Server bombs, and the Crystal Viewer says: SO when Crystal passes the SQL Query to SQL Server, it no longer references the tables with their schema name, i.e. On each of the tables, it looks like the schema name is lost. #Set owner of dbschema sql code#What seems to happen is that when we loop through the tables in our c# code to do the Some are under sql server schema "dbo", other under our schemas named "license", "location", etc. However, the problem that we have is that the tables in the report all have different database schemas. This report is shipped to our clients, who all have different database names, so at runntime we loop through all the tables to change the database name. We have a crystal report called license.rpt. We are working with VS 2010, C#, Crystal Reports 2008 Developer Edition ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |