Hello Fabio,
Most likely it's UDF problem. It was discussed a lot - search this list.
To track down crashes you can follow this guide:
http://www.ibphoenix.com/resources/documents/development/doc_35
To reduce the negative effect of the crash switch to Classic.
Regards,
Alexey Kovyazin
IBSurgeon
At 11:43 PM 5/09/2011, dkdoug.k707 wrote:
>I'm wondering if anyone knows what to do about this:
>I have three ISAPI applications running on IIS 6 on Windows Server 2003. They
>are written in Delphi, using IBX components to connect to Firebird 2.1.
>
>I have a critical bug. Here's what happens:
[.
Hi all.
I've installed Firebird 2.1.4 x64 on a machine with the following
features.
Windows Server 2008 R2 Foundation Service Pack 1;
Intel Xeon CPU X3430, 2.40GHz;
RAM = 8 GByte;
64 bit OS;
Hard disk = 136 GByte;
Sometimes, about 3 times per week, the Firebird server crashes with
following
I'm wondering if anyone knows what to do about this:
I have three ISAPI applications running on IIS 6 on Windows Server 2003. They
are written in Delphi, using IBX components to connect to Firebird 2.1.
I have a critical bug. Here's what happens:
* If I run the first application directly, it corr
Hello, i see that the field SQL$SECURITY_CLASS is char(31) and every value
in this field starts with 'SQL$'. Then every object, RDB$PROCEDURES and
RDB$RELATIONS whose length is greater than 27 char, can have the same
SQL$SECURITY_CLASS value. For example, The table
EST_CALIDAD_INCIDENCIA_PR_CAUSA
a
Svein Erling Tysvær wrote:
> SELECT "Date"
> , sum(Case when "Time" = '9.00' then "Issued" else 0 end) as "9:00"
> , sum(Case when "Time" = '9.25' then "Issued" else 0 end) as "9:15"
> , sum(Case when "Time" = '9.50' then "Issued" else 0 end) as "9:30"
> FROM Z
> GROUP BY 1
AH ..
Svein Erling Tysvær wrote:
> Lester Caine wrote:
>>> Do I end up with a list of fields each picking up one timeslot for a
>>> particular
>>> date? Or is there some way to use the 'timeslot' table that I used to use
>>> in the
>>> old two phase process?
>>
>> OK falling at first hurdle ...
>>
>> W
Svein Erling Tysvær wrote:
> Lester Caine wrote:
>>> Do I end up with a list of fields each picking up one timeslot for a
>>> particular
>>> date? Or is there some way to use the 'timeslot' table that I used to use
>>> in the
>>> old two phase process?
>>
>> OK falling at first hurdle ...
>>
>> W
Hi,
Thanks a lot for the help.
I now have the following working, except for the one-to-many relationships (two
of them).
With Recursive r1 as
(
Select t1.ID from BD_Locality t1
where t1.ID = :ID_RootLoc
Union all
Select t2.ID from BD_Locality t2
join r1 j1 on t2.Parent_ID = j1.id
)
,
r2 as
(
S
Lester Caine wrote:
>> Do I end up with a list of fields each picking up one timeslot for a
>> particular
>> date? Or is there some way to use the 'timeslot' table that I used to use in
>> the
>> old two phase process?
>
>OK falling at first hurdle ...
>
>WITH
> Z as
> (
> SELECT
>CAST (
Lester Caine wrote:
> Do I end up with a list of fields each picking up one timeslot for a
> particular
> date? Or is there some way to use the 'timeslot' table that I used to use in
> the
> old two phase process?
OK falling at first hurdle ...
WITH
Z as
(
SELECT
CAST ( T.TRANSACT A
I've got some legacy code that creates a temporary table of data which can then
be used to create a report, but I am quite sure that this can now be replaced
with a single CTE approach, and while I've got some quite nice multi layer
reports, one thing is still alluding me ... 2D grid ...
I now
12 matches
Mail list logo
