ACE Report Compiler Problem v4.0x to v4.1x

ACE Report Compiler Problem v4.0x to v4.1x

Post by Milt We » Wed, 29 Jun 1994 02:07:25



We experienced the following problem upgrading from ISQL v4.0 to v4.1.
Many of our reports will compile with the 4.1 product but produce the
following run-time error. (This is on an RS-6000)

        The column "" is not in the current table, or
        the user variable "" has not been defined.
        Source code line number 0.
        See error number -9004.

A call to Informix Support resulted in being informed that our reports
were to big for the compiler. These reports will compile and run under
the old 2.1 version on DOS -or- UNIX and run fine. The only work around
I had was to compile them under 4.0 (on an obsolete platform here) and
then ship the .arcs to the RS-6000 and SCO boxes. There was no compile
time error on these.

I can't beleive that the compiler broke going from 4.0 to 4.1 and that
Informix Support doesn't consider this a problem.

I would welcome a dialogue with any Informix staff frequenting this forum.
--
------------------------------------------------------------------------------



Norcross, GA 30092                 | Phone 404/840-1365(W) or 404/945-5896(H)

 
 
 

ACE Report Compiler Problem v4.0x to v4.1x

Post by Clive Eis » Wed, 29 Jun 1994 16:01:27



> We experienced the following problem upgrading from ISQL v4.0 to v4.1.
> Many of our reports will compile with the 4.1 product but produce the
> following run-time error. (This is on an RS-6000)

>         The column "" is not in the current table, or
>         the user variable "" has not been defined.
>         Source code line number 0.
>         See error number -9004.

> A call to Informix Support resulted in being informed that our reports
> were to big for the compiler. These reports will compile and run under
> the old 2.1 version on DOS -or- UNIX and run fine. The only work around
> I had was to compile them under 4.0 (on an obsolete platform here) and
> then ship the .arcs to the RS-6000 and SCO boxes. There was no compile
> time error on these.

We have a simlar problem with some reports on 4.0

Quote:

> I can't beleive that the compiler broke going from 4.0 to 4.1 and that
> Informix Support doesn't consider this a problem.

No I think they just changed where it was broke ;-)
However there seem to be two solutions.

1) Play with individual line lengths in your ace source until
the compiler will accept it. This seems to be the trigger.

2) Switch to isqlperl for your reports which is what we have
decided to do as it is a much more flexible tool!

> I would welcome a dialogue with any Informix staff frequenting this forum.
> --
> ------------------------------------------------------------------------------



> Norcross, GA 30092                 | Phone 404/840-1365(W) or 404/945-5896(H)

--

Clive Eisen Computing          Phone  (+44) 71 281 1414

 
 
 

1. Odbc v4.0 (v4.0.4028.0)

Hi,

The actual file to look for is: odbcjt32.dll. This file is currently at
v4.0.4028.0 and you can download it at:
http://www.microsoft.com/data/download/jetODBC.exe

You need to have MDAC v2.1SP1a (or v2.1.1.3711.11) installed first.
Got to: http://www.microsoft.com/data/download2.htm

If you do development work then use MDAC v2.1 SDK (5.6MB).b You also need
the older MDAC v2.0 SDK (37.5 MB).


2. Challenge for sp_spaceused Guhrus!

3. Oracle8.0.3 for Digital V4.0.a-V4.0.c

4. Best Method for Exporting data from Access to Excel

5. Wanted To Buy: FMPro Win v4.0 or v4.1

6. Searches get slow after a while

7. MS XML Parser v4.0 on NT v4.0

8. Re - Crystal reports(V4.60) problem in Client/server App

9. Problems with Crystal Report v4.6 + VB6 Pro and Access 2000

10. Crystal Report V4.6 Selection Formula

11. Visual Basic v4, v5, SQL, Oracle, Crystal Reports., Contract

12. begin with report on INFORMIX V4