Hello

1. I have created a report that connects to an Access Database
2. I have "converted to UNC" the path to the database.
3. I have saved the report to my web publishing directory.
4. I have "shared" the directory on my PC (NT4) where the Access database
is.

But, when i try to access the report thru my web browser - the report starts
to generate and then comes up with an error "creating data source failed"

anyone see what i am doing wrong ?

Dan

Trevor,

We have been using Crystal 6.0 Professional since Oct '97 and have been
distributing our reports to our user community via the web. Our software
configuration is : WinNT 4.0, IIS 3.0, MS-SQL Server 6.5.  

Running Crystal Reports via IIS, Crystal Web Server works fine for
"primary" data sources (tables, views).  However, if you want to run a
report which uses "secondary" data sources (query, sub-reports) you will
need to use Active Server Pages and the Crystal Reports Automation
Server.  The Seagate support staff have some excellent examples of using
ASP and the Crystal Automation Server.

One word of caution, if you are using the Automation server without a
VBScript or javascript frontend you would be wise to remove all prompts
from your report.

The "CREATING DATA SOURCE ERROR" typically results under any of the
following circumstances:
1. using Crystal Web Server to run a "secondary" data source report
(query, sub-reports),
2. the crystal web server (crpgsvr.exe) is hung,
3. the web server (inetinfo.exe) is hung.

If your error results from crpgsvr.exe or inetinfo.exe you will have to
shut them down.  You will probably be unsuccessful in your attempts to
"End Task" the crpgsvr.exe and your attempts to stop the WWW service
will sometimes fail.  Look around the web for a neat utility called
KILL.EXE which is the WinNT equivalent to the UNIX "kill -9" command;
this will permit you to kill both inetinfo.exe and crpgsvr.exe then
restart them.  With the WWW service stopped, find the crpgsvr.exe file,
double click it to re-activate the crystal web server, then re-start the
WWW service.  

Hope this helps.

Cheers,
        ... Chris.