>...
>A) If a user filters data from a base table using the SQL select menu,
the
>resulting "QueryN" query is saved in the workspace
>
>B) If a user uses the select tool to pick data from a map or browser
(base
>tables) and then either views the results (New Browser > Selection) or
maps the
>results (Add Map Layer > Selection) then the resulting "QueryN" table is
NOT
>saved to the workspace.
>
>I have no problem with this, except that I cannot get my application to
DETECT
>how each of the "QueryN" queries / selections was created.
Try mapping or browsing each query and then checking the results of
WindowInfo(FrontWindow(), 15). If it is not blank, then the window
can be saved and restored in a workspace. If it is blank, then the
window cannot.
Coincidentally, I just went through the same exercise. Although I
found the tidbit above, I could not find a way to detect which
thematic layers would be lost or saved. Instead, I created a tool
that helps the user explicitly save queries before they create
thematic layers based on them.
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
