Though it's lacking some of the goodness of the same operation in MS Office applications, there IS a way to save PDF documents to a SharePoint document library directly from Adobe Acrobat 7.

The first thing you have to do is set up a new Network Place in My Network Places. To do this, open My Network Places, and click Add a network place.  Follow the Wizard, and in the Internet or Network Address field, enter the full URL to the SharePoint document library.  For example, http://sharepointserver/Shared Documents.

Then, in Adobe Acrobat, using the Save As dialog box, click My Network Places, and choose the Network Place you created.

This process won't prompt you for item properties (i.e. SharePoint columns), but it does allow you to get things into SharePoint right from Acrobat 7.

Over on my OZ blog, I wrote a couple of posts about using folders in SharePoint lists and document libraries.  I bemoaned the use of folders in SharePoint document libraries and lists as a way to organize large quantities of documents. 

Finding something in a digital folder hierarchy can be impossible unless you already know the hierarchy. For example, I've seen top level folders in these hierarchies that align with a company's departments or divisions, beneath these are folders for fiscal years, then maybe some folders that describe activities.  What's the problem with this? If I'm new to the company, I pretty much need to understand the business before I can find the document I need.

It seems pretty natural to want to organize things just like you might in your physical filing cabinet, but a filing cabinet doesn't do things like search or filtering, and a computer doesn't expose things in a tactile way like a filing cabinet.  Back in the DOS days, if you had a folder hierarchy like the one I described above and you wanted to find a file with a certain string of characters in the file name, you could issue a command like this:

DIR budget*.xls /s

This would search through the hierarchy relatively quickly and list the files matching the pattern along with the folder in which the file resides.  In Windows, you could use Search, but it's fairly slow because windows has to parse through the contents of the hierarchy one file at a time.  Then along came desktop search which indexes the file system, making searches much faster. Nice, but we're still using a pretty blunt tool. What if we could label files with certain terms appropriate to our business and then quickly expose them based on those labels? 

We can add custom document properties to a file, but in Windows explorer, there's no way to include the custom property as a column and then filter or group on that column.  For example, what if I put all my files in one folder, and all my documents had custom properties called "Fiscal Year" and "Division"? Then, what if I could have a shortcut on my desktop that opened Windows Explorer and showed a list of files from my folder whose custom properties contained 2007 for Fiscal Year, and Manufacturing for Division?  Or what if another shortcut listed all the files in my folder, but grouped things by Division and then by fiscal year? This would be like a Pivot Table for your files... but to me it's like Microsoft gave us these Custom Properties and then didn't give us anything we could do with them.

The bad news is that the file system can't do this.  The good news is that SharePoint can. 

Custom Document Properties are metadata.  Being able to manipulate file listings based on their metadata is one of the core pieces of functionality in SharePoint.  My opinion?--- don't use folders in the file system OR SharePoint.  In a SharePoint document library, custom document properties can be promoted or demoted to/from the document library's columns (effectively linking the two). I believe we should use SharePoint, properly describe our documents with Columns (and/or custom properties), and then use custom views to filter and/or group based on these.  It gives you the ability to simulate a folder like experience, but it's important to note that in SharePoint, if you nest documents in folders, this doesn't work.

 I haven't had the time to confirm what magic makes this work, but I've got SharePoint and Adobe playing well with each other.  I'm using SharePoint 2003 and Adobe Acrobat 7.0 Professional. I can now:

1. check out a PDF file
2. Edit it in Acrobat (by choosing "Edit in Adobe Acrobat" from the drop down menu in the document library)
3. Save it (back to the document library)
4. check it back in

This is all just like the way it works in Word, Excel, or PowerPoint.

First, begin following the directions in KB article 837849, then when you're at step 2b, add the following text inside Mapping XML element: 

EditText="Adobe Acrobat" OpenControl="SharePoint.OpenDocuments"

so that the entire element looks like this:

<Mapping Key="pdf" Value="NameofIconFile.gif" EditText="Notepad" OpenControl="SharePoint.OpenDocuments"/>

Small business people can drown in paper. We see it here in our office. Every day, we get paper from all directions and we're never sure what do do with some of it. Seems like the day after you throw something away or shred it, you find you needed it.

 Solutions to scan to PDF have existed for some time, but Fujitsu has done a great job of making it affordable for small businesses.The ScanSnap S500 sells for less than $500 bucks Canadian, and has terrific output. It's as easy as pushing one button and a text searchable ("OCR-ed") PDF document gets saved into a folder of your choice.

Weaknesses? At first glance, there's little control over this thing programmatically, or beyond the out-of-the-box "ScanSnap Organizer". For example, on our Small Business Server network, our SBS server has network fax enabled. Wouldn't it be nice if this thing could be used to scan directly to this service without having to open up the document and "Print to Fax"?

Furthermore, with Windows SharePoint Services, and a PDF iFilter installed, these searchable documents can live in a document library whose contents can be indexed... that piece of paper can now be found by anyone in the company using SharePoint search. It would sure be nice if this thing had support for WSS out of the box...