Exa-Min wrote:
> I sympathise with your request. Actually, quite a few or our customers
> maintain a table view of the coordinates, and update that view to match the
> map locations after MapInfo editing. Or they want to drop points on a
> mapper and print out the locations for surveying contractors and the like.
Hi Exa-Min!
I do understand the need to 'see' coordinate values.
As I understand, you favor using populated columns in the static table
structure for that purpose.
My point is that the average user most often fails to understand that
such column values are disconnected from the graphic table component.
Consequently, the user believes that points should move when new values
are entered, or that values should change as points are moved.
In short, the practice is prone to possibly fatal errors.
This is why I always recommend the use of dynamic columns to show
coordinates.
A problem is of course the way MI defaults to lat/long values, but this
can as you surely know easily be overcome within applications.
Regards, Mats.E
--
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:Email/ [EMAIL PROTECTED] ICQ#9517386 :
:---------------------------------------------------------------------:
:Mail/ GISKRAFT, Mats Elfstroem, Vaepplingv 21, SE-227 38 LUND, SWEDEN:
:Phones: +46 46 145959, +46 70 595 3935 :
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
