SUM: MI-L SQL join and Info Tool, odd behaviour
Dear list, A join between a MI table and a RDBMS table with one-to-many relations makes the info tool present several records with the same data. The solution to this is saving the join as a new table and opening this table(!) as suggested by Simon O'Keefe and Steve Smith. This must be a bug! I have read-only data on a SQL server that is being updated regularily from outside the house. When I join data at runtime (with a workspace), the data is not presented correctly if I don't use the workaround. The runtime join makes the workspace work slower, but it means less maintenance work for me. Any suggestions? Regards Søren Breddam Teknisk Forvaltning Stevns Kommune Tlf. +45 5656 1891 ___ 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.
MI-L SQL join and Info Tool, odd behaviour
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.
Re: MI-L SQL join and Info Tool, odd behaviour
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.
Re: MI-L SQL join and Info Tool, odd behaviour
Hi Søren, I have experienced this problem too. As mad as I am that this bug has existed for so long, I have just accepted it and used a work-around. Save the new_table, then open it. The correct relationships will be restored. Cheers, Simon - Simon O'Keefe Groundtruth GIS Daylesford VIC Australia ___ 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.
