Yes, it does use rowid. The bigger thing to watch (with custom labels). DONT PACK YOUR TABLE! This totally screws up custom labels. However, if you have a workspace w/ custom labels, you can delete the custom labels if the workspace won't open. I'm pretty sure ROWID is the driver for all MI operations, including editing. I say this because when combining objects, I've often wondered about what data it chooses to keep. Again, the 1st row seems to be the one. Dan Dan Munson Director of Sales & Marketing CDS Business Mapping 800-746-7797 Mapping for the Next Millennium -----Original Message----- From: Cindy Reid <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Sunday, June 20, 1999 3:09 PM Subject: MI Obj order and the consequences in labeling... >As I am painfully aware, obj order is very important in maintaining an >appropriate link between a file, and the instructions within the workspace. > As I was sitting here "repairing" a map in which the labels rotated due to >the re-creation of two of the objeccts, thereby making Object 23, Object >21, I was lamenting how futile that process seems. I mean, I seem to be >faced with only two options. 1) Change the reference in the workspace >itself (ie change the object number where it has be written by the >workspace) or 2) relabel everything on the map, making sure that each label >is now in its correct place. > >But..... there has to be a better way. Then, as I thought about that more, >I realized that I fundamentally don't understand how MapInfo "thinks" about >object order. Is it truly tied to rowid? So that obj 1 is the first row >in the data? Or is there some other hierarchy?.... If Obj 1 is the first >row (record) in the data, then how does it account for unpacked records >(cuz they are counted as rows by rowid). How can you figure out which >object number goes with which object? If you could do that, then you could >add a field to any table from which labels will be called, then simply sort >on the obj_id, returning the "new" obj to it's place in the table.... But >that assumes that MI thinks about objects in record/row order, not in order >of creation...... > >Has anybody figured out a practical way to address this? It's one of my >favorite "gotcha's", and one I forget about on a daily basis.... until it >"getsme!". Frustrated in the afternoon...... >---------------------------------------------------------------------- >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]
