Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. VibrantIce

    Changing the XML "ReportLogon" info in c#

    Dell, Thanks. If I have time I'll look into the commit thing. Though I never needed the commit before when using database data sources. It's just the XML data source that's giving me grief. Also, I got an email from BO that said this method wasn't granular enough to properly update the...
  2. VibrantIce

    Changing the XML "ReportLogon" info in c#

    I'm trying to override the data source for a report that was deployed on BO XI. I have tried various permutations of the following code, and nothing works. Either the query uses the original data source or it doesn't run. The URL requires no password or username. What am I missing...
  3. VibrantIce

    Unknown Database Error with XML

    We reinstalled BO several times with the same patches, etc. as the legacy box. We installed a KB patch from BO that was NOT on the legacy box, and things suddenly started working.
  4. VibrantIce

    Parameter Page load time

    It looks like my problem was that JRE wasn't installed. Now that it's installed (manually), the parameters come up quickly. My reports still don't run ("Missing prompting unit" error), but at least the params don't take forever.
  5. VibrantIce

    Parameter Page load time

    We are experiencing this, too. Ours is version XI as well. My previous thread has additional details on the report. It works perfectly fine in the designer. It's just on the server where it is messed up. This is SOO painful!
  6. VibrantIce

    Unknown Database Error with XML

    It works fine in the desinger! We have a report that is using a HTTP data source (NOT a SOAP web service) that returns xml results which the report consumes. We point to an XSD for the schema. The report previews beautifully in the designer every time, no matter where the XSD resides...

Part and Inventory Search

Back
Top