Report DataSource Override

 3 Replies
 0 Subscribed to this topic
 22 Subscribed to this forum
Sort:
Author
Messages
Greg Moeller
Veteran Member
Posts: 1498
Veteran Member
    How would one do that??
    Matthew Nye
    Veteran Member
    Posts: 514
    Veteran Member
      that a bit light on details. for just basic creation and applying override data source the user guide could probably be more thorough than me, but I have a feeling youre beyond that. is there a specific question or issue youre looking to solve?
      If any of my answers were helpful an endorsement on LinkedIn would be much appriciated! www.linkedin.com/pub/matthew-nye/1a/886/760/
      Greg Moeller
      Veteran Member
      Posts: 1498
      Veteran Member
        Sorry for being so light on details yesterday.. I was in a bit of a rush and didn't have a whole lot of time to explain.
        MS SQL Server 2008 has a database that is using encryption (non-Lawson). I have a WAS data source configured and working that connects to this database, so was curious if I could get the over-ride data source to point to that. We're trying to over-ride the data source simply because we can't get 'use Report data source' to work. I think because of the data source used to develop the report, and the one configured on the RAS aren't the same.
        In the end, we just configured a new over-ride datasource and I think late yesterday we got it working.. but I still may have further questions to post here. I'll keep you updated.
        Greg Moeller
        Veteran Member
        Posts: 1498
        Veteran Member
          FYI-
          When you are overriding a datasource (at least for a 'Generic ODBC Connection') you have to default a schema. Turns out that this schema is passed to the RAS server and used, regardless of schema definitions in the actual report.
          Shouldn't this schema just be a default schema but also allow you to define others in your report?
          For example, I configured the override datasource, and just assumed that dbo was the correct entry to place there. A report written off of a different schema, runs fine in Crystal 2008 Developer, and even shows in 'View SQL query' the other schema being passed, but yet with dbo created in the override datasource, it was passing dbo.tablename to the RAS. Proven through log files on the SQL server.