Robin's SharePoint and Website musings

You're working furiously on a document with only a few minutes left until the doors close for the day (or your laptop battery dies, or some other emergency happens). You need to save the document to SharePoint, but you can't remember where the document library is in which you need to save the document.  If you make your frequently used Document Libraries Favorites in Windows Explorer.  That won’t be a problem again! Here's how to make it easier to save your documents to your SharePoint library: Create a Favorite in Windows Explorer.  Not in your browser (Internet Explorer, Chrome, Firefox, etc.). Let me show you what I mean: Figure 1: Windows Explorer Favorites So how did I get this screen? And how did I put the Shared Documents folder in my Favorites? This blog post will answer those questions. How to Get to the Favorites in Windows Explorer: I’m using Windows 7, so if you’re running XP, Vista, or Win8, your screen may lo...

InfoPath 2010 - In Form Approval - End User - NothingButSharePoint.com Thanks @nothingbutsp and Chris Grist for providing just the information I needed!

How to Distribute a Training Video with DocRead for SharePoint Another useful find as we move forward with our SharePoint upgrade project.

After adding a Security Certificate to our SharePoint server, we had an issue with the transaction log for the content database exploding exponentially taking up most of the remaining space on our SQL server. The site slowed down to a crawl and it was quick to see that this was a problem that needed immediate assistance. I knew it was possible to shrink an SQL database, but not having an SQL server background, I wasn't sure what implications that would have for our SharePoint system. So I did some research on TechNet and found instructions on how to do it. Then I contacted a DBA friend and started asking questions. I was pretty sure that I could write a job in the SQL Studio Manager to shrink the database and transaction log, but was an honest with my manager that I didn't know what repercussions it would cause. Thus we opted to call in a consultant. Turns out the consultant did exactly what I had found to do. We ran the shrink on the main content database without a ...