MapInfo Pro

Hi John,

The docs could be clearer.

From the help:

Note: When Filter is applied on a layer an internal hidden table is created.

You can use the LayerInfo(<mapId>, <layerNum>, LAYER_INFO_FILTER_TABLE_ALIAS) to get the alias of the hidden filter query table.

Then the syntax to refresh the table is:

select Update For table_name Refresh [All]

table_name: is the name of an existing query table. Query table should not be having any group by clause, aggregators (spatial, non-spatial), or derived objects and should have a where clause.

Refresh : Optional Token to refresh the query table map, browser, and theme. Specifying only the Refresh token will not recalculate the theme bins. To recalculate the theme bins, specify the Refresh All token. The Refresh token if used without a where clause will re-evaluate the queries' existing where condition, without closing the table and its dependent windows. This is useful in case the table data changes and the query needs to be re-evaluated.

Hope this helps.

Hi John,

The docs could be clearer.

From the help:

Note: When Filter is applied on a layer an internal hidden table is created.

You can use the LayerInfo(<mapId>, <layerNum>, LAYER_INFO_FILTER_TABLE_ALIAS) to get the alias of the hidden filter query table.

Then the syntax to refresh the table is:

select Update For table_name Refresh [All]

table_name: is the name of an existing query table. Query table should not be having any group by clause, aggregators (spatial, non-spatial), or derived objects and should have a where clause.

Refresh : Optional Token to refresh the query table map, browser, and theme. Specifying only the Refresh token will not recalculate the theme bins. To recalculate the theme bins, specify the Refresh All token. The Refresh token if used without a where clause will re-evaluate the queries' existing where condition, without closing the table and its dependent windows. This is useful in case the table data changes and the query needs to be re-evaluated.

Hope this helps.

Hi John,

The docs could be clearer.

From the help:

Note: When Filter is applied on a layer an internal hidden table is created.

You can use the LayerInfo(<mapId>, <layerNum>, LAYER_INFO_FILTER_TABLE_ALIAS) to get the alias of the hidden filter query table.

Then the syntax to refresh the table is:

select Update For table_name Refresh [All]

table_name: is the name of an existing query table. Query table should not be having any group by clause, aggregators (spatial, non-spatial), or derived objects and should have a where clause.

Refresh : Optional Token to refresh the query table map, browser, and theme. Specifying only the Refresh token will not recalculate the theme bins. To recalculate the theme bins, specify the Refresh All token. The Refresh token if used without a where clause will re-evaluate the queries' existing where condition, without closing the table and its dependent windows. This is useful in case the table data changes and the query needs to be re-evaluated.

Hope this helps.

Hi John,

The docs could be clearer.

From the help:

Note: When Filter is applied on a layer an internal hidden table is created.

You can use the LayerInfo(<mapId>, <layerNum>, LAYER_INFO_FILTER_TABLE_ALIAS) to get the alias of the hidden filter query table.

Then the syntax to refresh the table is:

select Update For table_name Refresh [All]

table_name: is the name of an existing query table. Query table should not be having any group by clause, aggregators (spatial, non-spatial), or derived objects and should have a where clause.

Refresh : Optional Token to refresh the query table map, browser, and theme. Specifying only the Refresh token will not recalculate the theme bins. To recalculate the theme bins, specify the Refresh All token. The Refresh token if used without a where clause will re-evaluate the queries' existing where condition, without closing the table and its dependent windows. This is useful in case the table data changes and the query needs to be re-evaluated.

Hope this helps.

Hi John,

The docs could be clearer.

From the help:

Note: When Filter is applied on a layer an internal hidden table is created.

You can use the LayerInfo(<mapId>, <layerNum>, LAYER_INFO_FILTER_TABLE_ALIAS) to get the alias of the hidden filter query table.

Then the syntax to refresh the table is:

select Update For table_name Refresh [All]

table_name: is the name of an existing query table. Query table should not be having any group by clause, aggregators (spatial, non-spatial), or derived objects and should have a where clause.

Refresh : Optional Token to refresh the query table map, browser, and theme. Specifying only the Refresh token will not recalculate the theme bins. To recalculate the theme bins, specify the Refresh All token. The Refresh token if used without a where clause will re-evaluate the queries' existing where condition, without closing the table and its dependent windows. This is useful in case the table data changes and the query needs to be re-evaluated.

Hope this helps.

Hi John,

The docs could be clearer.

From the help:

Note: When Filter is applied on a layer an internal hidden table is created.

You can use the LayerInfo(<mapId>, <layerNum>, LAYER_INFO_FILTER_TABLE_ALIAS) to get the alias of the hidden filter query table.

Then the syntax to refresh the table is:

select Update For table_name Refresh [All]

table_name: is the name of an existing query table. Query table should not be having any group by clause, aggregators (spatial, non-spatial), or derived objects and should have a where clause.

Refresh : Optional Token to refresh the query table map, browser, and theme. Specifying only the Refresh token will not recalculate the theme bins. To recalculate the theme bins, specify the Refresh All token. The Refresh token if used without a where clause will re-evaluate the queries' existing where condition, without closing the table and its dependent windows. This is useful in case the table data changes and the query needs to be re-evaluated.

Hope this helps.

Hi John,

The docs could be clearer.

From the help:

Note: When Filter is applied on a layer an internal hidden table is created.

You can use the LayerInfo(<mapId>, <layerNum>, LAYER_INFO_FILTER_TABLE_ALIAS) to get the alias of the hidden filter query table.

Then the syntax to refresh the table is:

select Update For table_name Refresh [All]

table_name: is the name of an existing query table. Query table should not be having any group by clause, aggregators (spatial, non-spatial), or derived objects and should have a where clause.

Refresh : Optional Token to refresh the query table map, browser, and theme. Specifying only the Refresh token will not recalculate the theme bins. To recalculate the theme bins, specify the Refresh All token. The Refresh token if used without a where clause will re-evaluate the queries' existing where condition, without closing the table and its dependent windows. This is useful in case the table data changes and the query needs to be re-evaluated.

Hope this helps.

Hi John,

The docs could be clearer.

From the help:

Note: When Filter is applied on a layer an internal hidden table is created.

You can use the LayerInfo(<mapId>, <layerNum>, LAYER_INFO_FILTER_TABLE_ALIAS) to get the alias of the hidden filter query table.

Then the syntax to refresh the table is:

select Update For table_name Refresh [All]

table_name: is the name of an existing query table. Query table should not be having any group by clause, aggregators (spatial, non-spatial), or derived objects and should have a where clause.

Refresh : Optional Token to refresh the query table map, browser, and theme. Specifying only the Refresh token will not recalculate the theme bins. To recalculate the theme bins, specify the Refresh All token. The Refresh token if used without a where clause will re-evaluate the queries' existing where condition, without closing the table and its dependent windows. This is useful in case the table data changes and the query needs to be re-evaluated.

Hope this helps.