Moving day has passed here at the thomasso.com site, and what a learning curve that was. If you were wondering what was going on in the last couple of days: seeing error pages, database failures, scrip errors and DNS no-comprehend, then you were witnessing the transformation of my move down South. Yes, the site now lives in California. I just wish I was there right now, but now it is time to fix all the kinks and links that are now broken.
Learning is one of those things that we as humans never stop doing, and we have a pattern of doing it just like the rest of the primate world, we need to touch it, then observe it and then call for help. Like for instance, we like to have things set up so that we can just press a button and expect it to work. Computers are a classic example of this relationship of man versus machine, perseverance over impossibilities and science over mystery. I press a button; the computer magically comes to life. However, when things go wrong, and they undoubtedly will, (this is the Male trait) we decide first to fix the problem ourselves. We unscrew the box in which all the hardware sits, and we begin to poke, pry, shake, pull, push, wiggle, swear, curs, hit, slam, bang, shove and sigh, then we get out the manual(s) and quickly start flipping through the pages, searching for that holy of grail, the page that will solve our problem: NOT! Once we have exhausted that avenue, we then begin to move into phase two of the learning curve: the search and destroy phase. This is where we go and start tapping into the hidden world of the software; we start throwing disks, one after another, until the damage is so irreversible, we begin to realize that we must consult outside advice: free of course. And free usually means someone who is just as knowledgeable as I am. It is not until we realize that the cost over runs of damage caused versus the damage initiated from the problem starts to out pace itself, we then realize that professional help must be sought.
I was lucky in that my problem was solved by taking the time in learning some simple commands and taking the time to read a few pages of text to solve the problem. However, the time it took to do all of this was about 10 hours, yet I gained more than I had before the move, and I am a better person now. I can now see why you should properly backup your database—-it is a must. I now have my system set to automatically backup every seven days. Not only does the backup occur, but it is done properly–as in the tables are intact. *smerk*