BryceEngstrom

The warning is helpful, and having the PDF open in the viewer right away for checking helps too, thanks. One could really get caught with one's pants down over an unnoticed failed overwrite.

On further inspection, it seems like it might have something to do with having the file folder with the PDF files in question open in Window Explorer when you try and replace. If I just go up one level in the file tree, so none of the PDF's in that particular file folder are being "previewed" in Windows Explorer, then the replacing happens correctly. But Chief's PDF converter should know it's not replacing properly.

This has been going on a while, and I am sure I sent it in before, but is anyone else having this issue? I don't think I ever got an answer. I go to Save as PDF in layout and want to overwrite an existing file. It asks me if I want to replace, I click Yes, but the new file is the same as the old file without the new revisions to the layout. So, I save it with the same name in a different location. That works. I try to move that file into the same file as the previous version, and it says I need permissions or something. I've tried to muck with those and it never seems to change anything. So, I just delete the previous version (why will it let me delete and not simply replace?) and then move the new version into the file where I wanted it in the first place. I know that part of it is a Windows thing, but Chief's PDF converter doesn't seem to know it's not replacing the file. Annoying waste of time.

I am not too concerned with the loss of the old forum. This one will fill up fast enough. I, for one, am really liking the design and usability of this one much better already. VBulletin seems archaic by comparison.

Definitely not one plan. Has happened in many plans. I am using Google Drive, but I am still opening a file from a local location. I find that I need to "pause" Google Drive when I am working with Chief because opening, closing, and re-opening a file can cause an error message (previously reported) that says the file has become locked. I have to restart the computer when this happens. But, if I pause Google Drive before I start working in Chief, I do not have this problem. So, it may or may not have something to do with Google Drive. I will try and pay more attention to that and if the vector view freezing happens when Google Drive is not paused.

I am still having a fairly consistent issue with having more than one vector view open and then having one of them just freeze. If it is saved, I can close and re-open, but it is just annoying. Impossible to replicated reliably, but annoying nonetheless. Anyone else having this issue?

The worst thing about this is having "Newbie" above my picture. Not sure I can live with that.