Having problem with the report components

Can someone please do the following procedure and see if the xojo crashes?

  1. Start a new desktop project.
  2. Add a new report.
  3. Add a report component eg. a report label.
  4. Select the component that was added.
  5. Ctrl-C to copy and Ctrl-V to paste…

At this point did xojo just crashed and died?

Confirmed OS X 10.8.4 / Xojo 2013 r2

See feedback://showreport?report_id=27889

That did not happened in Realbasic! It is not possible that xojo was re-written from ground or was it ?

I gave up on using their reporting tool years ago. It’s part of the reason why we created our own: http://www.bkeeney.com/allproducts/bkeeney-shorts/

A number of developers are using Shorts with great success. It’s strength: you do all the decisions. It’s weakness: you do all the decisions. It’s more work than a traditional reporting tool but you can do more with it than a traditional reporting tool.

It’s relatively fast. Depending upon the report we’ve seen speeds of about 300 pages a second. Exports to html and can create PDF reports (when using the DynaPDF plugin from Monkeybread Software).

[quote=20947:@Bob Keeney]I gave up on using their reporting tool years ago. It’s part of the reason why we created our own: http://www.bkeeney.com/allproducts/bkeeney-shorts/

A number of developers are using Shorts with great success. It’s strength: you do all the decisions. It’s weakness: you do all the decisions. It’s more work than a traditional reporting tool but you can do more with it than a traditional reporting tool.

It’s relatively fast. Depending upon the report we’ve seen speeds of about 300 pages a second. Exports to html and can create PDF reports (when using the DynaPDF plugin from Monkeybread Software).[/quote]

Nice

I just wonder. I see many members here working with web apps, but I don’t see many members having a site made only by Xojo web development

You have to remember that Xojo Web Edition is NOT for making web sites. It is meant for web apps as part of a website. I have my Xojo Training which is a web app that’s been running for about a year and a half now. Served up over over 5,500 hours of Real Studio/Xojo training video. It’s at http://www.bkeeney.com/XojoTraining/xojotraining.cgi and is just part of my website.

But is bkneeney-shorts able to handle Japanese and chinese fonts?

It should. I don’t know specifically but you can take it for a spin (you can modify the demo) and if it doesn’t work properly for you we’ll work with you to get it working (since that’s a high want for many people).

Other possible solutions are to make reports in Microsoft Word or Microsoft Excel. Unfortunately this only works on the Windows environment.

Looks like XOJO has no intention of solving this problem?
I’ve reported this error in the feedback and I’m not the only one. They said it has been fixed and awaiting testing…just left it there!
Kind of disappointing!!!

Very disappointing! I waited to buy RS until they came out with the reporting. I purchased thinking they would improve it over the years. I’ve seen very few improvements in it over the years and finally purchased MBSDynaPDF for reporting. It turned out the be a good solution. I just hope the future for Xojo IDE is better than the reporting tool. Right now I’m not to impressed.

Thank you for reporting these.

I was in a hurry (as usual) earlier this year and do not have time to learn that technology. So, I wrote my own routines to print my simple reports (text only) (PDF).

Two weeks ago, I was starting to get an eye on Report (Reports) ?

First try: no result, second = same… 'till today: no result. (I mean: I am unable to understand how to use it to fit my needs).

So, I will let time do its job 'till I have more time to learn it / XOJO set it better.

Conceptually, it is very easy for me to use it; I use a bunch of softwares who had this kind of technology long time ago. But knowing the concept is one thing, applying it to your needs is another. I need more than time to plunge in this technology.

Since Xojo does not use the Reporting tool in any of their products the feature set is limited. And, because they don’t feel the day-to-day pain with it, the bugs don’t get fixed as quickly as others.

I believe that if they made a product that actually uses their own reporting tools they would get much better, very quickly. Instead, it’s kind of marketing bullet point and will languish.

Hello Everyone,

Similar to the issues that everyone was mentioning about the reporting tool, I dove into the deep end and created many example to try and explain this in plain English. Unfortunately, it is for working with Microsoft Access which is Windows OS only. See Book Link , Table of Contents Free Preview .

What I have found with the Xojo team is that I need to have a laser-like focus with issues to help them squish bugs. Becoming a specialist with Access and the reporting tools makes it easier to develop slimmed-down example programs for the Xojo programming team to see the issues. Also, I get to push-the-envelope on the abilities of the reporting tool and provide some helpful feedback.

Having a business major background, when working within any company there are always ‘internal-issues’ and I am sure that Xojo has its own details to work out. Helping Xojo determine the issues quickly will likely get the problem(s) fixed quickly. This is kind of the Carrot and Stick Approach . Does this always work - no, does it usually work, yes.

Just my $0.02,

Eugene

The built-in reporting is patchy at best. We build primarily database apps and we have numerous reports in all of them. I so wish they would show the reporting system some love. If we get really stuck we use ODBC to connect to MySQL and Filemaker Pro for reports.

The cut and paste thing is just a new frustration…

[quote=23120:@Benny Lee]Looks like XOJO has no intention of solving this problem?
I’ve reported this error in the feedback and I’m not the only one. They said it has been fixed and awaiting testing…just left it there!
Kind of disappointing!!![/quote]
It’s fixed in an as yet unreleased version

Bob:
Since Xojo does not use the Reporting tool…
This argument have been used 'till RS use RS to create RS. I had strong hopes in that theory, but my hopes vanished. And, I think it is a dead horse, so stop beat it. What good does it gave us ?

In short, I do not believe anymore in this argument. If they have to make report(s) for any reason, why will they use this tool (buggy tool as you and others seems to know) ?
They’s better create a another one for their own use (specialized for that task).

They used in RS a window splitter whatever name it really have, but we do not saw one for our own use (and yes, I do not even think “what if I will be able to create one by my own ?").

As times goes by, I feel that to get the best from (now) XOJO, one have to license plug-ins / use OS API as widely as possible “et vogue la galère !”.

Nota: this is not a rant, but rather a report based over years of experiment (and low, very low rants).