Hi,
some time ago, I post a message about the precedence of ADD COLUMN
statement vs SELECT statement in workspace file. No response came. Briefly,
what I intend to do is to create a thematic on a road network. The data used
is International Roughness Index (IRI). The classes are divide into
deficiency level (High, Average, low, none). The range for each class is
different from one road class to the other (For high deficiency for
Highways, the IRI>3.5, for collectors, IRI > 5). So what I need to do is a
2D thematic. For each road class (4), I have 4 level of deficiency. To get
it more complicated, I have the IRI data on a table, and my road network on
an other. The two are join with a common field. The way I proceed now is:
- Join my tables through an UPDATE COLUMN (Add Temporary Column)
- Execute 4 queries to separate my road according the the road
class.
- Put the 4 queries in a map, a create a thematic for each one.
It works great at run time, except I can't use my workspace again since all
the Select statement are run before my Add Column. I have to manually,
change the order in the commands, each time I save the workspace. Of
course, I try to join my queries with the IRI table, but I can't. Only base
tables can be joined. My wish is that I can create multiple field thematic
(at least 2). So, read my previous message again. Maybe you will understand
my disarray.
I hope someone from MapInfo will explain the precedence of statement in the
workspace, especially SELECT vs ADD COLUMN. Since tables create from query
can't be join, there's no reason to put ADD COLUMN statement after the
SELECT statement.
Another glitch with the UPDATE COLUMN dialog, although MI Reference Guide
says otherwise, you can't add a temporary column to a Read-Only table, since
the table is not accessible in the popup menu. In the MapBasic Window, I can
do it. In the thematic dialog, I can do it. So why not in the Update Column
dialog ?
Maybe I'm asking a little bit too much. I presume that someone have
encounter similar problem, so they could tell me what they've done about it.
I hope that MI is listening and taking notes, so that in the next release of
MI, I will no longer have to play with my workspace.
Have the nicest Xmas holidays !
Yannick Leduc
P.S. I'm in out of the office until January 5th, so I will be disconnect
from the list. I will catch up on the digest though...
=-=-=-=-Previous message =-=-=-=-=-=-=-
Hi all,
Is there someone who figured out how workspace files are written
(the first part of it). Here's some lines from one of my workspace causing
me a little problem.
---Workspace snippet ---
Open Table "C:\Donn�es � mettre sur le serveur
CARTO\DT64\Confort\DT64_MIchau" As DT64_MIchau
Open Table "C:\Donn�es � mettre sur le serveur
CARTO\DT63\Confort\DT63_MIchau" As DT63_MIchau
Open Table "C:\MapInfo\TempGPS\DT_RTS" As DT_RTS Interactive
Open Table "C:\Donn�es � mettre sur le serveur
CARTO\DT64\Confort\DT64_MIchauSect" As DT64_MIchauSect
Select * from DT_RTS where CL_FONCT = "10" into AUTO64 noselect order by
RTS
Select * from DT_RTS where CL_FONCT = "40" and chaussee <> "0" into COL64
noselect order by RTS
Select * from DT_RTS where CL_FONCT = "30" and chaussee <> "0" into REG64
noselect order by RTS
Select * from DT_RTS where CL_FONCT = "20" and chaussee <> "0" into NAT64
noselect order by RTS
Select * from DT_RTS where CL_FONCT = "10" and chaussee <> "0" into AUT64
noselect order by RTS
Add Column "DT_RTS" (IRI_�T�) From DT64_MIchauSect Set To IRI_�T� Where COL1
= COL1 Dynamic
Add Column "DT_RTS" (IRI_HIV) From DT64_MIchauSect Set To IRI_HIV Where COL1
= COL1 Dynamic
Open Table "C:\MapInfo\Donn�es\MTQ\Graphiques\Fleurdelyse" As Fleurdelyse
Interactive
--- End ---
Notice that the "Add Column" statements follow the "Select" statements
causing columns IRI_�T� and IRI_HIV to be missing in my queries. However, I
used these columns further for a thematic layer. So, opening my workspace
cause it to crash.
---Workspace snippet ---
Set Map
CoordSys Earth Projection 3, 33, "m", -70, 44, 50, 46, 800000, 0
Center (632000,236000)
Zoom 124 Units "km"
Preserve Zoom Display Zoom
XY Units "m" Distance Units "km" Area Units "sq km"
shade 4 with IRI_�T� ignore 0 ranges apply color use all Line (1,2,255)
[...]
--- End ---
I would like to know what justify the statement order in a workspace and if
there's restrictions to put "Add Column" before "Select" statements in a new
and improved version of MI.
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
