Subject | Re: [Firebird-Architect] Can we, can we, can we????... |
---|---|
Author | Jim Starkey |
Post date | 2005-06-14T21:15:21Z |
Dmitry Yemanov wrote:
isn't going to know how to continue after a canceled request, so nothing
is lost.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376
>"Ann W. Harrison" <aharrison@...> wrote:They should kill the report which should kill request. Crystal Reports
>
>
>>I guess I don't understand your web-server example.
>>
>>
>
>Let me suggest you another one. You have an ERP database and some
>applications. The used FB database is quite big and complex. Your users
>create necessary reports in Crystal Reports which connects to the server via
>EasySoft ODBC driver (BDE/dbExpress/whatever else). Our API cancel feature
>is not available for Crystal Reports. But users can easily forget some join
>condition when linking a few huge tables. If this reports implies sorting or
>complex stored procedures, your server is guaranteed to become hard loaded
>for a few hours (or even days).
>
>
>
>
isn't going to know how to continue after a canceled request, so nothing
is lost.
--
Jim Starkey
Netfrastructure, Inc.
978 526-1376