MapInfo Pro

If I move a label of a database table in a map (usually because it's covering something that needs to be shown as well), then save workspace, close workspace and return to the workspace later, the label has returned to it's original location and a new incorrect label from a different location is showing. We are running MI Pro 21, however this has happened since back in 17 or maybe earlier.  We are using autolabels for this.  We found a recent support article that mentions this , again we are already using autolabels.  One other thing to note is that our data is kept on a sql server, it's sql 2019.  The data was uploaded using the tool from MI.  Here is an example, you can see the black lines from where the incorrect labels came in from.  Imgur

Imgur		remove preview
Imgur Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users. View this on Imgur >

Hi James

Yeah, this is a known issue with custom labels. A custom label is a label you modify in some way, for example by moving it to a new location or changing its font.

When MapInfo Pro saves these custom labels to a workspace, it uses the ROWID of the record that the label refers to.

Unfortunately, there are a few situations where the ROWID isn't that stable:

• If you pack a table with deleted records, the ROWIDs will change
• If you refresh a table from a database or a WFS service, the ROWIDs will change
• If you reopen a live (with/without cache) table from a database, the ROWIDs may change.

We have an idea covering this issue on Precisely Ideas.

If I move a label of a database table in a map (usually because it's covering something that needs to be shown as well), then save workspace, close workspace and return to the workspace later, the label has returned to it's original location and a new incorrect label from a different location is showing. We are running MI Pro 21, however this has happened since back in 17 or maybe earlier.  We are using autolabels for this.  We found a recent support article that mentions this , again we are already using autolabels.  One other thing to note is that our data is kept on a sql server, it's sql 2019.  The data was uploaded using the tool from MI.  Here is an example, you can see the black lines from where the incorrect labels came in from.  Imgur

Imgur		remove preview
Imgur Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users. View this on Imgur >

If I move a label of a database table in a map (usually because it's covering something that needs to be shown as well), then save workspace, close workspace and return to the workspace later, the label has returned to it's original location and a new incorrect label from a different location is showing. We are running MI Pro 21, however this has happened since back in 17 or maybe earlier.  We are using autolabels for this.  We found a recent support article that mentions this , again we are already using autolabels.  One other thing to note is that our data is kept on a sql server, it's sql 2019.  The data was uploaded using the tool from MI.  Here is an example, you can see the black lines from where the incorrect labels came in from.  Imgur

Imgur		remove preview
Imgur Discover the magic of the internet at Imgur, a community powered entertainment destination. Lift your spirits with funny jokes, trending memes, entertaining gifs, inspiring stories, viral videos, and so much more from users. View this on Imgur >