Dear Hypersizer,
Good Morning
Please read attached Word document for the pictures referenced (where the * appear) in this post.
I am using Hypersizer version 6.4.52
I am wondering if you would be able to help me trying to create an effective laminate, I have done this previously in earlier versions but seem to be having a little trouble this time around.
I have created a quasi-isotropic lay-up in the Laminate Materials family,
I right click on the quasi-isotropic laminate and review laminate material. This brings up the Laminate creation table with all the data of how the laminate is made up.
From this form I select ‘Analyze Laminate and calculate equivalent orthotropic materials” and the Effective laminate Properties windows is open with all the data and options.
I have chosen the numerous options and failure criteria and the clicked the button labelled “Analyze and Save As EL..” and that brings up another window labelled “Save As Effective Laminate…” I have filled in the boxes, Material Name, Form, Specification, Basis and Bending correction Factor
When I click OK I get an error message that reads –
*
If I click OK I get
*
Then two windows are opened
*
If I look at the Event Viewer I find the following message
*
I have tried numerous different options to overcome the error message
• I have created a new Laminate and tried to create the effective laminate and this still get the same error message.
• I have filled in the Material Name, Form, Specification, Basis and Bending correction Factor as new and unique strings and I got the same error message.
After reading the Event log I have tried to understand if it was my user policy and weather that would affect the creation of the Effective Laminate. However having read the help file, I must have “User” Access as I can create projects and material data. So I am unsure if this is the problem.
Is there something fundamentally that I am doing wrong, in the creation of the Effective Laminate or is it a function of my current settings/privileges?
I have tried this on both our networks that we currently use and we have the same problem on both networks.
Thanks
Martin