Use Area() unless you're taking a big performance hit somewhere.
There are three area functions:
SphericalArea() measures areas on the surface of the Earth, using spherical
trigonometry calculations. It's theoretically more accurate, but is more
complicated and takes more time to calculate.
CartesianArea() measures areas of objects as if they were drawn on a flat
plane, using analytic geometry on coordinates referenced to table's
coordinate system, if that table is in a projected coordinate system. This
theoretically takes less time to calculate, but it's less accurate, and if
the table is in a lat/long coordinate system, it returns an invalid result.
If your study area is small, the difference between the two should be
negligible.
Area() abstracts the two so you don't have to decide: it uses
CartesianArea() if the data is in a Nonearth or Layout coordinate system,
and SphericalArea() if it's in an Earth coordinate system.
For each given project that you want to use this function in, you want to
select one or the other, based on the project's requirements, and use it
consistently.
ATTN MAPINFO:
It's a bit weird that CartesianArea() skips the "current coordinate system"
and goes right to the table's coordinate system. If you've set the current
coordinate system to some projected coordinate system, you should be allowed
to extract areas using CartesianArea(), even if the table is in lat/long.
HTH
________________________________
Spencer