I use Crystal with Delphi.  I have had absolutely no help from their 
support email address.  I finally complained to the president after 
two weeks of continual email.  That produced the help that I needed.  
It turns out that if you mis-fill their forms, they are just junked.  
And the beggars insist that no one else has any problems with the 
email support.  There are various other issues such as 
misinformation in articles in various mags and I wouldnt recommend 
Crystal to anyone.

I have already written to the editors in question asking them to stop 
doing their readers a dis-service by stopping any future articles on 

Your problem does sound like missing or mismatched DLLs.  They are a 
mess with different version number working with each other etc... and 
they almost never complain about the mismatch of version numbers, 
instead you get starnge non-sensical messages.

On 11 Mar 99 at 7:40, Belding wrote:

> Thanks Steve for your comments. I'm using the 16bit Dlls from CR ver
> CR help replied within an hour to a request made at their WWW
> site with several things to try. Particularly doing a comparison of DLLs
> loaded on a PC when the reports run OK and on an NTWS4 box where the
> repoarts all fail. The tool to use for this is their DSX.EXE (16bit).
> The most likely cause is a missing DLL, I think. Would you agree?
> At worst I could strip all the reports out into a D4 program, even if that
> meant installing two BDEs on a server.
> RB
> At 23:15 10/03/99 +1300, you wrote:
> >
> >-----Original Message-----
> >From: Belding <[EMAIL PROTECTED]>
> >To: Multiple recipients of list delphi <[EMAIL PROTECTED]>
> >Date: Wednesday, March 10, 1999 5:26 PM
> >Subject: [DUG]: Delphi and Crystal on NT4
> >
> >
> >>Hello team
> >>
> >>Anyone using Delphi with Crystal Reports on NT4?
> >>
> >
> >32 bit Works well. If you have 16 bit tools Seagate Software  will not help
> >you if you are a Delphi developer either. You will likely have little joy
> >with versions prior to 5.x.108 and anything other than 32 bit Delphi. The
> >Seagate developed VCL wrapper around crpe32.dll for v5, 6 or 7 is more
> >powerful than the COM/VB equivalents.
> >
> >>With NT 4 (sp?) the reports won't run and I get an error "cannot open
> >>database" from the Crystal DLL.
> >
> >You will have to specify the database type, database version,
> >Crystal Reports type, version, platform and the method you are using to
> >interface with the Crystal Reports Print Engine DLL i.e OCX, CRPExx.dll
> >imports, VCL (D2,3,4, CB1,3 with source) or the Automation Server, as well
> >as the version of the BDE, ODBC, ADO, or native connection you are trying to
> >hook up to Crystal Reports.
> >
> >Sounds like a configuration issue."Unable To Open Database File" is an OCX
> >error which implies a Database verify may be required or the pathname is too
> >long esp wih Access, or maybe some UNC pathing problems. If you are using an
> >ActiveX bridge to Crystal Reports then there are a host of OS and Microsft
> >DLL redistributables to factor in.
> >
> >>
> >>Any insight would be hugely welcome.
> >>
> >
> >
> > and  /pub/seagate_crystal_reports is
> >full of software samples, fixes, extensions etc. Http access gives you some
> >of this:  You
> >may find benefit by consulting the newsgroups hosted at or
> >the alternative Crystal Report VCL at or end user info @
> >
> >
> >
> >p.exe
> >is a handy test tool written in Delphi with source.
> >
> >Cheers,
> >Steve Cooney
> >Pacific Windows
> >
> >---------------------------------------------------------------------------
> >    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
> >                  Website:
> >
> >
> >
> Russell Belding
> Belding Computing Devices
> ---------------------------------------------------------------------------
>     New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
>                   Website:

CFL - Computer Fanatics Ltd.  21 Barry's Point Road, AKL, New Zealand
PH    (649) 489-2280 
FX    (649) 489-2290

    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]

Reply via email to