Optimize Your Web

After needing much documentation on both installation instructions, I need to reiterate the importance of documentation for both yourself or future readers.  I had a large project that I was completing with a colleague and after having to upgrade, reformat, and reconfigure many machines (around 20-30), I had many programs that had no documentation at all.

Reasons you may not realize why you should document:

-Just because you finally figure something out, does not mean that you will at a later time or that the next person will figure it out. If it’s not already written, write it down, even if it’s a temporary fix. It may turn into the only fix or help you find a permanent solution later with more information or further knowledge.
-Something that may seem simple to you at that time, may not be simple later or to the next person. So if it is not common sense, DOCUMENT!.

And documentation should extend to keep all licenses together and safe. It’s very hard to tell a customer that you cannot help them because they do not have their license with them. And for all types of documentation and licenses, do one thing and keep them protected. I would recommend buying something like a firesafe that they can keep those and extremely important records such as portable media backups of tax information, databases (if you do not have off site storage as well as on site for redundancy). While a fire may be devastating, it may be a breath of fresh air to know that you still have some things safe.

Recently, I had to work on some Quickbooks for a client.  One thing I noticed is that there are so many ways to botch a configuration or install if you are going off of someone else’s work.  Regardless, if you are running a database server with Quickbooks, and are installing the Single-Host client on machines, make sure that you have added your folders to the first tab in the Database Manager for Quickbooks, and allowed it to scan.  Once this is done, you should be good.

Another thing you may encounter is a program called Yardi.  If you do, make sure that wherever your files are located (I was lucky enough to have two sets of data for different purposes), write down what users have what access to those files.  In my case, the people trying to access both sets of data had to log into one, then open another database and change the location.  It was not giving them a choice for the data, so you must log on with whatever user has access to the first one you setup and then switch to the second.

If anyone has problems with either application, comment on this article or contact me via the Contact Me form and I’ll see if I have any insights.  Good luck, and make sure you always document.

After having to reformat a friends machine, I figured there were people who need a little guide or a list of helpful hints to guide them on their way.

(continue reading…)