Jos;

I enjoy the term “best solution” as it is so subjective. It means many things to anyone you ask. Some things I take into consideration are:

1. User needs.
2. Budget
3. Time line.
4. Security.
5. Data integrity.
6. Communication!

Every client’s requirements are different. I program in a number of different languages and platforms from mainframe to desktop and also take tools into consideration.

There are many ways to be successful in any undertaking and computer programming is no different. Some ways may be “better” than others but if it works and meets client needs then it is “the” solution. Anyone can be a critic and say, “I would have done it differently”, but that is not important to reality. Anything can be done “better”. Reality in this case is what is being used.

Most important to me is to be honest and up front with everyone. I have no need to spread bs to make a positive impression. I do make an effort to find out all I can about a topic before I consider a solution. It is important to think before you act, use your experience and always try to do your best.

By the way your comment about a hammer and nail reminds me that I love to buy and use tools. As an example I have more than a dozen different types of hammers from a delicate jewelers hammer to a 10-pound sledgehammer. I use the latter when all else fails! :)

Tom




>Hi Tom
>
>I think your points on preventing database corruption is quite on the mark. Of course they apply to any database that one uses and are simply common sense. And I also agree with you iro using DBF and DBC. I find they work for the type of appplications I develop.
>
>I find that topics like these are more often about using "what I know" rather than using the "best solution". To a hammer everything is a nail? (To managers everything needs to be nailed and to employees - well, we are the nails :)
>
>On top of which "best solution" is also often a difficult point to quantify. And how many of us actually have the knowledge and experience of both sides of the coin to be able to judge. I know I dont. Too often subjective preferences are presented as objective proofs.
>
>And one crucial aspect is almost always overlooked. All the "best technology" in the world won't make up for a bad implementation. (Which is why there's so little hope for me!) To ruin a phrase - I would rather have an average technology solution implemented well than the best technology solution implemented by me poorly.
>
>Go Well.
>
>
>
>>>>
>>>>1. Have a clean and stable source of primary power.
>>>>
>>>>2. UPS supplies in case of power loss.
>>>>
>>>>3. Be aware that computer power supplies that are 3 years or older may become a source of data corruption due to deterioration of components, which can place voltage spikes on the output filtered voltage.
>>>>
>>>>4. Good cables, and Hubs (switchers, etc.).
>>>>
>>>>5. Define which operating systems and service packs are being used by each computer and be aware if there are any concerns about how they handle data.
>>>>
>>>>6. For Novel use the latest patches and seek out answers before there are problems. Determine if the version or versions of Novel you use have known problems by asking others in the community.
>>>>
>>>>7. Peer to peer is a touchy topic, which can work well with two or three computers.
>>>>
>>>>8. Use of a product such as Stonefield Database toolkit to repair damaged tables or indexes without user intervention.
>>>>
>>>>9. It is important to have a good data backup strategy and be sure that it works! On one occasion my back up media was defective and luckily it was not needed. That is an experience I will never forget. When you buy the best tape and expect it to work and does not it is your problem.
>>>>
>>>>These are some of the things I would consider. There are many versions of Novel and each one has had some “interesting and unique” behavior while performing such things as handling data or printing.
>>>>
>>>>Tom
>>>>