Custom Reports using DSD SQL Mirror

SUGGESTED

We recently started using the DSD SQL Mirror to speed up reporting and are very pleased so for with the results but I have run into a problem.  I am attempting to move the slower reports in SAGE custom report menus over to the mirror and when I attempt to run it within SAGE it defaults back to the SOTAMAS90 DSN.  i am assuming there is a trick to getting it to override the default.  I already tried the "Converted to version 5.20" trick that I have used with custom reports that run off Access Db's.  Is the solution to set up an access Db with passthroughs to all the mirrored tables?  That seems kind of a clunky solution.

Thanks in advance this forum has always been very helpful!

Parents
  • 0

    Set up a system SQL DSN on each workstation (with users given SQL permissions), and set the report to use that DSN.  The main caveat is that the company code is never dynamic, if you have multiples.  If that doesn't work, do the same thing with a hollow SOTAMAS90 report (something quick like a query of SY_Company, with everything suppressed) and set up your report as a sub-report (in the report header or footer), with the sub-report data source being the SQL DSN.

  • 0 in reply to Kevin M

    I tried a Sotamas90 report, selecting just the SY_Company filtering for just the company code we mirror, suppressed everything, inserted my report that is connected the the SQL DSN and still get the error on the dates because it's still pointing to SOTAMAS90 (it runs fine outside of SAGE)  Thanks again for the help!

  • 0 in reply to up4a
    SUGGESTED

    Try to reset the database location with in Crystal Designer for that report. See KB 56742 and 69138

Reply Children