Phin,
I can't comment on the deployment being expensive (user licensing) since I
might be implementing it differently.
As I understand it, if you are creating the app with the CR reports embedded
in the app, then there are no additional licensing fees. However, if you
include the ability for the end-user to customize the reports with their
additional DLLs, then there is a licensing fee required since you are
essentially deploying a copy of their product IDE to the end user.
I have no problems with that since my clients cannot customize our
"standard" reports.
We recommend to them that if they need "customized" reports that they can
either (1) buy CR 9/10 or (2) import the data from the database tables into
Excel, etc -- using products that they are more familiar with already. For
my clients, a lot of them are already familiar with CR since it is the
report backend for things like SAP, PeopleSoft, etc ... if I recall
correctly.
My biggest problem is the fact that CR.NET is included with VS, but is not
supported to the same level as BO's "main line" products like CR 9/10 ... if
BO is not going to support it the same as CR9/10, then MS needs to consider
a different partner for the VS.NET reporting tool set.
Ron
"mrwoopey" <mr******@yahoo.com> wrote in message
news:e4**************************@posting.google.c om...
Thank you for your feedback!
I'm sick of Crystal! It's a pain and expensive to deploy (user
licensing!).
I'm thinking of ditching Crystal and going for Microsoft's Reporting
Services which is basically free if you have at least a SQL 2000
server! Also, Reporting Services is easier to develop than Crystal!
Crystal is going to keep loosing users (like myself) if they keep not
supporting their product and if licensing doesn't go down!
Phin