Changing to font size 11 seems to solve the problem.

@epostma 

Good to know that you found the reason.

Just to make sure, the eval should be done when reading values from the DataTable component, or when writing values? And does it need to be done on each of the elements of the table, or the table itself?

P.S.: My experience with last name evaluation has already led me to the "meme" in the title - if in doubt, always use "eval". I'm already using it on countless occasions.

@Carl Love 

I've managed to create a simple example which shows the issue.

InvalidSubscriptSelector.mw

This is getting even more mysterious now.

• The error message happens just when running the workbook after a new start of Maple, or reopening the worksheet.
• The error only comes when operation includes a force and a moment. In that case the force is multiplied with a distance (which gives a moment) and added to the existing moment.
• Two forces work well together.
• The moment itself is also no issue.
• As I said, entering the values after a reset doesn't show any problems either. In that case, the values are stored in a global variable. The problem arises when the table values are read from the storematrix after a reopening of the workbook.
• I've attached the contents of the Matrix that stores the values. This one is then attached to the (invisible) Data Table Component.
• 

@Carl Love 

Took some time to convert the workbook to a worksheet, but actually it was quite useful.

The main issue was related to storing the load table values in a one-dimensioned Matrix. And here I'm getting a bit confused, because I couldn't reproduce the problem after fixing it.

Fixing in my case was to reset the loads, which reset the stored values in the Matrix that stores values between sessions.

When storing or reading values, I usually used storematrix[1,1] to do that. After converting to the worksheet I got an error message about out of boundary, so I could just use storematrix[1] to save values, not storematrix[1,1].

I've run a test, and for storing values, storematrix[1] is that same as storematrix[1,1]. When reading values again, it becomes different, as storematrix[1] returns the value as a vector, while storematrix[1,1] actually gives the stored value.

During all of the test I checked the contents of the variables, and nothing looked suspicious. So right now I don't know what the reason of the problem actually is.

Thanks a lot for the quick response.

@tomleslie 

That actually leads to another question.

Why isn't Maple able to work with its own predefined constants? I mean, what exactly is the meaning of "use Pi for calculations" according to the help file.

Regarding the conversion - this is something new in Maple 2022.

@Preben Alsholm 

I could do at least 3 other methods to go around the problem again, but frankly speaking I'm fed up of the Units package.

There are far too many bugs in this implementation, and apparently its gets worse.

Apparently the solution is to use evalf on the contents of alpha.

I'll add this one to the list...

https://www.mapleprimes.com/questions/234028-Maple-2022--New-Bug-In-UnitsSimple

About 3 years ago we came to the conclusion that Mathcad wasn't worth the bucket anymore, and we landed on Maple as the alternative. By coincidence, both software houses have now delivered their new releases.

And the situation is the same as the last couple of years. While I would need about a day or more to dig through all the changes of the Maple package, the new things on the Mathcad front are, well, limited.

So on that front a big applause to the Maple development team.

I do however have a couple of issues that I am not so happy with, and that need to be addressed as soon as possible.

• Maple still hasn't any functional system in place to prevent two users from opening the same workbook. The last to save wins is not a game we want to play in our office. This is basic functionality that is lacking, guys, and you've been made aware of it for quite a long time now.
• The units package is still a mess. The biggest issue is that variables miss their unit when their value becomes zero. In addition some functions miss part of their functionality once you add units.

On the other side, Maple 2022 seems to be more responsive, and has fewer graphics glitches than we had previously. 

Autosave finally seems to work for workbooks as well, and some progress has been made on the pdf printing front.

@vv 

That's exactly why an exemption should be raised in that case.

Contrary to plan Maple, the Units package doesn't implement the [index] functionality anymore, thus it is unknown.

If the max function doesn't ignore wrong indices, the max function in the Units package should'nt do either.

Apparently fixed in 2022.

@Karen 

Solution verified.

However Maple Help still only mentiones autosave for worksheets, not workbooks.

No change in Maple 2022.