I've just found that when the demo is poorly done, oftentimes the product is, too. Or the developers have an attitude similar to the one you expressed (if you can't figure it out, you're a weak developer). I need tools to make my life easier not to present me with poor demos and poor docs and expect me to take the time to figure out what they could have explained better. As for the sample code. They state it can be used "as is" and yet they put the CLOSE DATABASES command in it. Whatever. I'm looking at MindsEye now anyway . . .


>Hi Russell,
>
>I'm not saying that you are a weak developer, I'm just astonish to see that when I tried the demo, I knew that those two line of of code were only there for demo purposes. Maybe I knew that because I'm used to provide demo software to my customer and that's why they call it a demo.
>
>But anyway, I'm kind of surprise to see that small details like those can generate bad critic upon this product. When I first tried it with my report, I didn't have to change a line to get my report out in any desired format. For me that whas very impressive, It minimized the work I had to do to get the Frx in the desired format. I didn't use the actual demo to integrate in my software, I used it as a sample.
>
>I purchased the Dev edition package and found it very weel coded as for the classes, the objects and the code itself.
>
>If you find the demo lame, the two line of code non-professionnal even if the product give you great result just don't purchase it. I'm just expressing an opinion.
>
>Like you said it yourself, the demo gives the wrong impression for a great product.