masemenos:
First, in your previous post you said that I put more or less put words in your mouth. Sorry about that, it was never my intention. When I wrote "you" in that sentence I did not mean you personally. I meant "you" the analyst as in anyony doing the analysis, but that wasn't clear. Sorry about that.
Then you latest post. You say that I have made a mistatement of facts regarding structural FEA. In what respect?
Havent we agreed on that structural FEA can't do all FEA tasks? That's what I stated, nothing else.
And I wrote "steel frames etc", I was never specific regarding the "etc". That wasn't an accident

.
Finally, when I stated that it shouldn't get "TO nonlinear or TO dynamic". I was thinking about things like contact like multibody-contact of moving bodies. Or material models like hyperelastic. Or ......? Greg mentioned crash analysis.
Note: I don't think I have claimed that EVERY general software can do all of the above mentioned. But a general pre/post processor can usually "talk" to one of the solvers that can.
Sure, we can look specifics like you do and claim that structural FEA is just as good. It might be for some applications. You for example mentioned response spectrum analysis in your previous post. The "fake mass" that sometimes is used. There is nothing "fake" about the large mass method. I think it comes from the aerospace industri. And there are often other options in general FEA if you don't like "fake mass", unlike structural FEA.
If you think I've made an error and unfairly critizised structural FEA. I was just trying to point at some differences. Mayby I have faied miserably.
You have been very specific about the capacity of SAP2000. Since this tread is about Robot I have tried to keep it more general. I have colleges who have tested both of them and they have their pros and cons. At the time I thing Robot was considered better partially due to the connections with Revit. And it shold be possible to get the model from Robot to a general software but that might require some programming of the API.
I'm convinced that whatever software you intend to buy you need to test it and make sure that it fits yur needs. If you end up in the structural or the general "world" is not really important.
As for SAP2000, the reason we skipped it there were two problems if I remember correctly.
First, when we look at the results. For the design we needed max/min moments (envelops) and the associated axial forces and shear. We could only get max/min of everything. It worked if we used the internal design engine but since we had other code requirements it didn't work. We needed everything "on paper".
Second, bridge loads. We needed more general loadtrains then were available. Like for example, two or three concentrated loads (or loadgroups) moving independantly of each other. Now the code has changed so it might be enough with two loads (or loadgroups) independant of each other.
Regards
Thomas