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.
