Thanks. I will give that a shot tomorrow On Jun 3, 2009, at 6:34 PM, Gokhan Soydan wrote:
> > Arthur, > > Actually, there might be two options as work-around for preview: > > 1-) From the menu, select "Run > View Report", and a format that you > want to view the report in. You may be able to view your report there. > > 2-) Increase the JRE memory allocation. Close TBC, in the installation > folder for TBC, open the file "eclipse.ini" and replace the text > "-Xmx512m" with "-Xmx1024m". If Eclipse issues an error at re-start, > please give a smaller number than 1024 until it works on your machine. > > The reason is that BIRT sometimes consumes a lot of memory (or more > importantly contiguous memory I suspect) during preview/report > generation. I would also advise checking with BIRT support on memory > issues if you feel that they seem more internal to BIRT. > > Gokhan > > > Gokhan Soydan wrote: >> Arthur, >> >> Hmm, I didn't realize that there were problems of running TBC and >> BIRT >> together in Mac. I will look into this for later releases. >> Unfortunately, I don't know a work-around for now. >> >> Gokhan >> >> >> Arthur wrote: >> >>> I have experienced issues running BIRT when I use TBCM (all versions >>> since I started using it last year) in OS-X. It works near >>> perfectly >>> on Windows, but I would prefer to work on my Mac, so I have been >>> testing this on each new release of TBCM. >>> >>> When you launch BIRT from a query, the data does not seem to make it >>> over to the BIRT side. After adding a chart to the form and >>> attaching >>> to a TopBraid data source, no data is displayed in the preview and >>> although some meta data, i.e., property names comes through, the >>> property types do not - all the properties come over to BIRT as type >>> 'string' . If you bind the columns to a graph and try to preview >>> it, >>> TBC (i.e., Eclipse) will immediately crash. I have tried editing >>> the >>> BIRT Property types to the correspond to TBC types, but it did not >>> help. (I sometimes encounter the string type issue on windows and >>> modifying the types in BIRT seems to help). Holger and Scot >>> mentioned >>> other work-arounds for OS-X and I wonder if there is a work-around >>> for >>> this. >>> >>> Thanks >>> >>> Arthur >>> >>> >>> >> >> >>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
