CrystalRpts Vs. Access; FeatureByFeature?

[darrylqa]

Hi,
I just started a new job and need advice. Where can I
find information on the advantages and disadvantages of
Crystal Reports Vs. Microsoft Access Report Generator
when compared side by side? Examples of issues I am
interested in are:

(1) User interface when preparing to run a report.
(There could be many variables such as: Store Numbers,
Dates, SalesPersonID, etc.) (I am proficient with Access
VBA code and can easily create user-forms with drop-down
lists, checkboxes, etc. How does Crystal compare? How
easy is it to input variables from another program, such
as C# or VB, into a Crystal Report?) (I am new to Crystal
Reports.)

(2) How well does Access work with a SQLServer back-end?
SQLServer is our primary back-end software. (I am new to
SQLServer.)

(3) Convertabitlity: What if we eventually go to a Visual
Studio (C#) based information system. How easy does
Access convert to another report generator?

(4) We do have some Web Based applications. How does
each work with ASP's? (I am new to this.)

I looked till I was bleary-eyed last night for a good
pro/con, side by side feature article without any luck.
I'd appreciate any help. Thanks,
~darrylqa

 

[Larry Linson]

If my application was Access, I can't imagine using Crystal as the reporting
tool. I've seen some impressive work done with Crystal (by someone who'd put
in his time climbing the learning curve) in a case where it was appropriate
(a web-based application), but the person who did it said he'd choose Access
reports any day, if there were a choice.

You can, likely, drive Access via Com automation from .NET languages to
continue to use your Access' reports. It may take a little planning and
implementation to get printed copies down to the users, but it can be done.

If I were looking at an alternative to Access' reporting, I'd look into
Microsoft's SQL Server Reporting Services (separate product), especially for
the move to .NET.

Larry Linson
Microsoft Access MVP