AnsweredAssumed Answered

ExecuteSQL  ( calculation field not store )

Question asked by Draco on Dec 7, 2018
Latest reply on Dec 7, 2018 by Jason Wood

Hi,

 

I have 2 tables,

Table A (4000 records)

Table B (15000 records)

 

In table A, exist 10 fields that add different segments from table B.

 

 

(do not pay attention to formatting errors.)

FIELD 1

ExecuteSQL (    

    Select sum ( b.value )...        SIMPLE

    from b    

    where b.year = ?

    ...  ( ; "" ; "" ; 2019 )

)

 

FIELD 2

ExecuteSQL (    

    Select sum ( b.value )

    from b    

    where b.year = ?

    ...  ( ; "" ; "" ; 2018 )

)

 

.

.

.

FIELD 10

 

___________________________________________________

The 10 fields of table A are calculations (not stored)

___________________________________________________

 

In 99% of cases the query is for 1 record from table A, in few situations the 10 fields of all the records from table A will be displayed.

 

Question : it is recommended to implement these 10 fields with ExecuteSQL ?

 

I ask for comments about the slowness of ExecuteSQL

 

regards

Draco

Outcomes