Jaromir,
yep there is a little bugginess in 5 and 5.5 however I just did a test on
some of my geological datasets (points, line, arcs, ellipses, polys
scattered allover the place) and I can only replicate your second problem
problem one is resolved thus:
>>>>Fetch Rec n From Selection Print MyTable.RowID
should read:
Fetch Rec n From Selection Print selection.RowID
mapinfo will return max row number for a table with no fetched records (your
syntax fetches from the selection, but then prints from the base table)
problem two is harder to explain:
>>>>>Add Column TabName (RowNum Integer) From TabName Set To RowID
does create the bug you mentioned, however, again, your syntax is unfamiliar
to me because Mapinfo doesnt normally let you create a temporary column from
a single table (it normally does temprary joins via two tables), the methods
|i use to add rownumbers to a single table are:
alter table tablename (add rownum integer)...followed by
update tablename set rownum = rowid
this is a clunkier solution, and requires pending edits to be saved etc etc
but it does return the correct result..perhaps someone from MI can explain
why the dynamic column bombs on the non-polygon objects.
HTH and regards
Russell Lawley
Geoscientist
British Geological Survey
www.bgs.ac.uk <http://www.bgs.ac.uk>
_______________________________________________________________________
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.
