>maptitude CAN join tables.
i was thinking of append. maptitude cannot append; if you have two files of
counties, one of one state, and one of another, you can't put them together
into the same file.
>maptitude DOES have SQL.
maptitude has select by condition, but it does not have SQL, or if it does
it isn't in the documentation. maptitude's select by condition does not have
the functionality or the flexibility of mapinfo's SQL. it can't take two
different tables as inputs, it can't make calculated columns (aggregates)
and it's doesn't have as many operators or the same functions.
i still think everyone should buy it. :-)
bob rogers
>
>
>>here are several differences that i am aware of:
>>
>>maptitude cannot join tables.
>>maptitude does not have SQL.
>>maptitude can't rotate symbols.
>>
>>maptitude has a better geocoder
>>maptitude makes better looking maps
>>maptitude offeres more types of thematics.
>>
>>if it was me, i would wait for the new version (shipping real soon now),
>and
>>buy that instead of the mapinfo upgrade.
>>
>>bob
>>
>>
>>>On Mon, 10 May 1999, Charlie Richman wrote:
>>>
>>>> However, you'll find very rapidly that there are lots of
>>>> things it won't do -- large chunks of functionality and
>>>> little things that you assume it will do, but it won't.
>>>
>>>
>>>Can you give examples. (Since you said "large chunks" I'm hoping for a
>>>large number of examples!) I'm seriously considering buying Maptitude,
>>>and am very interested in your critique!
>>>
>>>Margie
>
>
>Mark
>
>----------------------------------------------------------------------
>To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
>"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
>
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
