I thought you could lock cells without requiring a password.

QuoteLocking cells in Excel makes them non-editable by default. First, make sure the cells are unlocked by checking them under the Format cells menu. Then select the cell/range of cells you want to lock, locking them again under the format cells menu.
Enforce this by protecting the worksheet. Your select cells are non-editable now, without a password.

I have a spreadsheet I'm creating in Excel to track jobs through the shop. In it I have some formulas to math for me. Problem is, it's really easy to accidentally delete or erase the formula and screw up the cell, so is there a way (without locking or requiring a password) to protect the formula inside that cell so it doesn't lose it's format and can still be typed in to? I know how to lock it, but then you can't add any new information, and the only other trick I know requires a password every time you want to add new information. Also, without the use of a 3rd party plug-in, is there a way to make a cell have a date finder calendar?

Nothing involving Vecna, but I've heard reports of sightings of Pinhead in Finishing, but that's been going on forever. Other than that Corn has it down.

Also, I've been told it's much less of a problem on the Indigo 7R. Still happens sometimes, but much much less often. No reports of it happening on the Ricoh or Oce BW machines.

I'm still waiting for him to run the test file I created from a job that went fine for J. We'll find out if he ever did it when he gets in in a bit.

The 3 prepress operators should switch computers for a week and see if the problem follows the operator or stays with the computer. That could point to a software setting somewhere. 

So I just want to clarify:

J imposes a file in the QI plugin in Acrobat. J saves it to your server directory. The Digital Press Operator opens his RIP and navigates in the software to J's file and clicks, import, and it's right side up, peachy and smelling like a rose.

You impose the same file the same way in the QI plugin in Acrobat. You save it to your server directory. The Digital Press Operator opens his RIP and navigates in the software to your file and clicks, import, and it's upside down?

Have you seen any demogorgons or made an offering to Vecna?

They'd be the files generated from a step and repeat in QI+, which ever way fit the most up without any additional rotation applied by prepress. They are using the same queue for almost all of them, so I'd imagine they'd have the honor rotation setting the same on at least the vast majority.

It really sticks out to me that is so divided us. Almost all of mine, almost non of J's. But I can't for the life of me figure out how it happens or what's causing it.

BTW, I did upgrade my computer and Pitstop last week, but that did not change anything either. Was happening before, and at the same rate after.

Are any of these pages rotated in the pdf file? I have gotten some of these before and had a similar outcome. It's where a one page pdf was added or merged into another pdf and the orientation was different (landscape instead of portrait) so they rotated the page in Acrobat to make it better.
It only shows up when the "honor rotation" was not checked at the RIP.

Not sure if that would apply in your situation.

The 12k only has 29.5x20.75 and 29.5x20.75. Both sizes do it if I set it up, both sizes don't do it if J sets it up. There has to be some kind of setting or meta data thing. He's about to run the test file we created that's already worked fine with J proofed it, but I went and reset it up as a test. Really interested in how that comes out.

what are the sizes of the files?
for us it happens to 18x12 (Landscape)
and not to the 12x18 (Portrait)
maybe make a log of the sizes/orientation that it's happening to
and you might find a pattern

As I said earlier, MOST of my files have the issue, but  not all. Most of the files created by J are fine. But I can't find any settings or meta data in the PDF that my software would be doing to create the problem. They always import the same way, so if that was the problem we'd all be having the same outcome. Any workflow to correct the problem automatically would just reverse the situation. We need to figure out what the root cause is to address it besides the manual way they are doing now.