Soren, I have experienced/discovered this too in the past, and have reported it to MapInfo, they say it is due to the way that MI handles one to many relations (sorry cant find the correspondence), but I think its just a bug in the info tool!! or at least a design feature they need to sort out.
Dave
>>> Søren_Breddam <[EMAIL PROTECTED]> 01/10 8:03 am >>>
Dear list,
When I make a SQL join like:
SELECT *
FROM MI_table, RDBMS_table
WHERE MI_table.id = RDBMS_table.id
INTO new_table
and add new_table to the map, I sometimes get odd results with the Info
Tool. This behaviour occurs when the RDBMS_table contains two records
with
the same id (e.g. two owners of a building). The Info Tool displays two
identical records, but new_table contains two different records from the
RDBMS_table joined to one object.
Can anyone tell me how to get this to work properly?
TIA
Søren Breddam
_______________________________________________________________________
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, send e-mail to [EMAIL PROTECTED] and
put "unsubscribe MapInfo-L" in the message body.
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**********************************************************************
_______________________________________________________________________
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, send e-mail to [EMAIL PROTECTED] and
put "unsubscribe MapInfo-L" in the message body.
