JST
Alibre Super User
Well, just now Alibre decide to LOCK the master BOM file for the project. I already had to rebuild it once..... I REALLY do not want to rebuild it YET AGAIN.
If it is any help to you, I had added some parts to it, and moved them from the bottom of the list to their proper area. I was just in the process of filling in the part info (in the part file, not editing the BOM) to match the BOM category prefixes (PL# for plate steel, for example, where # is the reference number for that part within the category.... Then the drawing gets labeled with the PL19 (in this case) as a find number in the drawings.
In the other thread, there was mention of "unblocking". What are you talking about with regard to "unblocking"? Where are you doing this? Because this file has never been off the "disk" (it's actually solid state)
If you mean with the OS, the file has never been read-only there. This is something that Alibre is doing internally, as far as I can determine. And I cannot blame it on memory leaks now, since resource monitor does not show a deficit now.
I just checked the file properties, and the OS has it as an openly writeable file.
Since this is not a new issue, it already happened once in Alibre, I do not like that it has happened again, making it now twice in three days. This trend is not good.
If it is any help to you, I had added some parts to it, and moved them from the bottom of the list to their proper area. I was just in the process of filling in the part info (in the part file, not editing the BOM) to match the BOM category prefixes (PL# for plate steel, for example, where # is the reference number for that part within the category.... Then the drawing gets labeled with the PL19 (in this case) as a find number in the drawings.
In the other thread, there was mention of "unblocking". What are you talking about with regard to "unblocking"? Where are you doing this? Because this file has never been off the "disk" (it's actually solid state)
If you mean with the OS, the file has never been read-only there. This is something that Alibre is doing internally, as far as I can determine. And I cannot blame it on memory leaks now, since resource monitor does not show a deficit now.
I just checked the file properties, and the OS has it as an openly writeable file.
Since this is not a new issue, it already happened once in Alibre, I do not like that it has happened again, making it now twice in three days. This trend is not good.