Trouble importing a STAAD / .str file

[bjur]

I am having trouble importing a staad file.  I know on this forum others have found it easy.  I have yet to get a staad file to open in Robot.  I went through the .str file and filled in all of the member names that were "MISSING".  I still get syntax errors on lines that look fine.  Any ideas?  Posted below is the staad file, and str file that I cleaned up.  The file has steel sections from India.  Not sure if this is causing all the trouble, but the sections that Robot is calling warnings on do exist in the indian database.

[Artur.Kosakowski]

I haven''t got enough time to check all but definitely you need to add information about material (e.g. add Steel line as shown below). In addition you should add MC 600 section to the database (either Indian or user defined) or replace it temporarily with another one (e.g. HEA 100). Hope this helps.

SUPports

1 TO 8

PROperties

STEEL

1 TO 4 MB 400 GAMma=90

You may still have some issues with the definitions of the combinations but to check the above type END before combination block and try to open such file.

[bjur]

I've reached a dead end with the import process.  I can't seam to get it to import.  I always get errors, even though the errors referenced don't appear to be errors.  Not sure if Robot is reporting the wrong line when reporting errors in sytax.

[Artur.Kosakowski · Accepted solution]

Please try to open the attached file.

[bjur]

Thank you!  So now I'm wondering, how did you do it?  I see the warnings regarding the steel size that doesn't exist in the database, but how did you get the rest of the "Syntax" errors to go away?

[Artur.Kosakowski]

As I wrote I added material name STEEL and created cases 21 to 24 so which are used in definitions of the combinations so that they are correctly 'read'.

[Pawel.Pulak]

The detection of lines with syntax errors in *.str text files was corrected starting from Service Pack 2 to RSA 2013.

Clicking error message should highlight appropriate line in STR file.

It will make analysis of such files and detection of possible syntax errors easier.

Regards,