Ben - thanks for the info. I did more checking, and the DLL is in fact on
my older server (now used for testing only) whose CF lineage began with CF
2.0. The DLL was in the SYSTEM32 directory for the NT 3.51 root, which is
what OS was running back then. I tried coping it over to the SYSTEM32
directory in the NT40 root, which is what I am running now. That made no
difference. I also tried copying it to the \CFUSION\BIN directory, no luck
there either (but, oddly enough, the error message came back a lot faster!).
SO, it looks like I have the DLL (dated in 1996), but cannot figure out how
to get CF to find it. Any ideas? I'm hoping that once this gets resolved,
and the server gets rolled to CF5, that the new CFREPORT still knows how to
use the old Crystal engine, and not just the newer version, 'cause there's
no way I'll get the bucks to buy that from Seagate!!!
thanks!
-reed
------------------------------
Date: Wed, 15 Aug 2001 11:01:59 -0500
From: "Braver, Ben" <[EMAIL PROTECTED]>
Subject: RE: CFREPORT and the Crystal Server
Message-ID: <CF3232998D6CD311A5B50020AFFC2E6802A7B5DC@AVNNTX01>
Reed-
CF used to include the CR engine.
It doesn't anymore.
You have to buy CR separately, sorry.
BTW when you do get CR and try <CFREPORT> search for the threads about
#GetDirectoryFromPath(CF_TEMPLATE_PATH)#
HTH
-Ben
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
