You are currently reviewing an older revision of this page.
The following error shows up when opening a model with user table General type section defined with profile points,
“ERROR, BLANK SPACE NOT ALLOWED BETWEN USER TABLE NAME, NAME TRUNCATED."
The error is being caused by the fact that the coordinates for the profile points are being erroneously written in the same line as the PROFILE POINTS command as shown next
...
START USER TABLE TABLE 1 GENERAL TEST1 0.185382 2.45833 0.037705 0.864583 0.107209 0.171605 0.005117 0.000142 - 0.137038 0.011722 0.097421 0.073301 0.162697 0.019352 0.007307 2.38292 PROFILE_POINTS -0.4323 1.2292 0.4323 1.2292 0.4323 1.1771 0.0208 1.1771 - 0.0208 -1.1771 0.375 -1.1771 0.375 -1.2292 -0.4323 -1.2292 -0.4323 -1.1771 - -0.0208 -1.1771 -0.0208 1.1771 -0.4323 1.1771 STRESS_LOCATIONS -0.4323 1.2292 0.4323 1.2292 0.375 -1.2292 -0.4323 -1.2292 END
.
Steps to Reproduce
Open a model with a user table General type section defined with profile points, The following error would pop up
Open the STAAD.Pro command file in the editor and move the coordinate for the profile points to the next line as shown next
START USER TABLE TABLE 1 GENERAL W30X90NOTCH 0.185382 2.45833 0.037705 0.864583 0.107209 0.171605 0.005117 0.000142 - 0.137038 0.011722 0.097421 0.073301 0.162697 0.019352 0.007307 2.38292 PROFILE_POINTS
-0.4323 1.2292 0.4323 1.2292 0.4323 1.1771 0.0208 1.1771 - 0.0208 -1.1771 0.375 -1.1771 0.375 -1.2292 -0.4323 -1.2292 -0.4323 -1.1771 - -0.0208 -1.1771 -0.0208 1.1771 -0.4323 1.1771 STRESS_LOCATIONS -0.4323 1.2292 0.4323 1.2292 0.375 -1.2292 -0.4323 -1.2292 END
Once the data is Saved from within the editor, the file should work without any problem. However please note that if the file is saved using the graphical user interface (GUI), the data would be rewritten in the incorrect format resulting in the same error as before. So if you need to make changes to the model using the GUI, it would be better to copy the user table commands and keep those in the commented out state so that the correct commands may be reactivated at a later stage.
Solution
The problem will be addressed in the STAAD.Pro Connect Edition Update 4.