Submitted by Armando on 2014/11/06 16:18
Fields based on queries freeze IQ.
This was mentioned in this older thread to the  forefront  (IQ loops on field defined using SQL SELECT).
 
I hadn't used those in a while, but it happened 10 min ago and thought I should mention... even if only a few users are using those (they are quite powerful and helpful though!)
 
 
Here's the request that freezes IQ :
 
SELECT FirstName AS Responsable, IDItem FROM Adrsbook
 
All the above fields exist, of course.

Comments

Dear Pierre
 
My bug report - see Armando's back-link - is outstanding since July and has not been fixed. This is a serious issue for me. This used to work and no longer does.
 
Mark GREGORY, Redon, France - GMT +1/+2; EST +6

OK, I was able to reproduce the issue. It is fixed in v0.9.26PreRel35
 
The lock up occurred when there was an error in the SQL for the drop down editor.
Now, the message is shown and the user can click OK to dismiss the dialog. The user can then open the field properties to correct the incorrect SQL code.
 
 

Armando

2014/11/07 12:26

In reply to by Pierre_Admin

Many thanks, Pierre ! :-)
 
-------------------------------------------------------
Windows 8.1
Sony Vaio S Series 13 (SVS131E21L)
Ram:8gb, CPU: Intel i5-3230M, 2.6ghz

Armando

2014/11/07 12:37

In reply to by Pierre_Admin

I don't think was there an error in my SQL statement, was there?
 
-------------------------------------------------------
Windows 8.1
Sony Vaio S Series 13 (SVS131E21L)
Ram:8gb, CPU: Intel i5-3230M, 2.6ghz

Armando

2014/11/07 13:19

In reply to by Armando

@Mark:
 
With Pierre's help, we've discovered that if the grid isn't set as being visible, the SQL statement will fail. This option is relatively new and can be set in the:
 
Manage grids dialog ->Options->Grid visible to other applications.
 
-------
So, for that statement, where AdrsBook is a grid:
 
SELECT FirstName AS Responsable, IDItem FROM AdrsBook
 
... the AdrsBook grid must be set as visible to other applications.
--------
 
That said, the freeze problem won't happen in the next version as the error will be managed differently and the user will get the chance to make the appropriate corrections (SQL syntax, set grid(s) as visible)
 
 
-------------------------------------------------------
Windows 8.1
Sony Vaio S Series 13 (SVS131E21L)
Ram:8gb, CPU: Intel i5-3230M, 2.6ghz

gregory

2014/11/07 22:16

In reply to by Armando

Many thanks to both Pierre and Armando.
 
Mark GREGORY, Redon, France - GMT +1/+2; EST +6

gregory

2014/11/07 22:52

In reply to by Armando

Two extra comments / thoughts on this post:
 
  1. I'd like to update the manual to include a comment to the effect that the grid must be set as being visible for the SQL SELECT statement to work. Please can I confirm with you that the only place in which the SQL SELECT statement is documented is at www.sqlnotes.net/drupal5/index.php?
     
  2. Pierre: can I remind you of a thread of five years ago where you discussed moving to a better environment for developing Visual Basic and in particular SQL SELECT statements – you will find that at www.sqlnotes.net/drupal5/index.php. Would moving to VSTA be difficult or expensive? And if it isn't, please can you do it quite quickly?
 
Mark GREGORY, Redon, France - GMT +1/+2; EST +6