Just upgraded my iMac at work to Mac OS X 10.6 Snow Leopard.... finally!!!!

But still running CS4 with Acrobat 9 (v9.5.2)

I edit master files using MS Word that are saved on my local server.

I distribute those files as PDFs saved to another server.

When updating files under Mac OS X 10.5 Leopard, printing with the PDF printer driver, I had a very fast simple work flow:

   Cick Print (Adobe PDF Printer was the default),

   navigate to the desired folder,

   click on the file to replace and then

   click Replace.

But under Snow Leopard, this workflow is now messed up:

   Click Print

   Click Continue in Save to Adobe PDF popup menu

   navigate to the desired folder

This is where the mess really starts.

If the file is new, not an update, and I just want to save it, "Microsoft Word - " is always prepended to the file name, and there is always a dual extension: ".docx.pdf" So I **always** have to edit it.

If the file is being saved as an update, when I click on the file to update, the file name no longer has an extension, not even a hidden one, just nothing at all. This is OK as far as Macs are concerned, the file still shows as a PDF file in Get Info. But Windows PCs (where these files will be used) no longer have a clue as to file type. So I **always** have to type ".pdf" after the file name.

   Finally I can click Save or Replace

And, if for any reason, I click "Cancel", Save to Adobe PDF **always** says "an error occurred while saving the PDF".

So... in this day and age, why isn't this any smarter???? Why is this app making me work more????

1) Is there any way to bypass the annoying unwanted PDF Settings/PDF Creation popup menu so I don't **always** have to click Continue??? Why isn't there a Preferences / Options menu item for this so I can pull it up only when needed???? Why always interrupt my workflow????

2) Is the default file name with "Microsoft Word - "  prepended to it an Adobe action or an MS Word action???? Who do I complain to about this??? Its possible that this is an MS Word abberation, as test prints in MS Excel and Mozilla Firefox don't show this problem.

3) Why do I have to keep screwing around with extensions???? Can't someone do some intelligent programming to make this simple and automatic for the user??????????????

4) in the normal course of pressing offered buttons such as Cancel, I should never see an error pop up.

Now, when I get home today, where I'm running Mac OS X 10.7 Lion with CS5, I'll have to see if this is any smarter.