
CR Automation Server vs CR ActiveX Controls ?
The main difference is that the active X controls basically seperate you the
programmer from the actual Crystal Object model (a.k.a. Automation Server).
The Automation server is a COM object which you can manipulate through code.
What we have found is that using the active X control limits you to having
your reports link to the database (Add database to report) directly in the
report.
Crystal basically sucks when it comes to data access. Its very slow, and
filled with bugs. With the Automation Engine you can use the Active Data
Drivers and .ttx files to basically assign recordsets to the reports at
runtime. We built an entire reporting manager application using this
technology (VB6, MTS, SQL Server, ACCESS, and Crystal 6 Pro).
It all depends on the skill level of the programmers that are going to use
the app. If you have programmers who are familiar with COM servers, and
using objects (Most basic VB Skills) then you should have no problem with
the Automation Server. If the programmers are green, than the ActiveX
control makes it very simple to add reports.
Let me know if you have any questions.
Scott Lock
Quote:
>Dear All,
>I get confused with CR Automation Server and CR ActiveX controls, i'm not
>sure which of them should i use from my VB application. Wish some1 can
>kindly tell a little bit about that.
>Thanks.
>Jcwy