>>>Hi friends:
>>>
>>>I have a client who has a single net (XP) and from time to time system "jumps" (quit violently) and the most common problem is a corrupted CDX. Today was a table. As it is a movement table they hadn't been able to continue working if I hadn't been here...
>>>
>>>If the problem is a CDX I can solve it with VFP commands and functions. For tables I bought a "third-party repair utility " as VFP's help says. That's how I could repair it today.
>>>
>>>I think I'll be able to sleep tonight but I don't want to say "You can't make any sale note before I arrive by steping the red carpet you must deploy for me..."
>>>
>>>Repairing tables using the "third-party repair utility" is quite easy and I know there are several Apostles of "Universal User Instructions Church" but most of my clients has a different religion. One of their Commandments is "I don't pay you for arranging system problems by myself"
>>>
>>>Among so much marvelous low level functions you can find here, do you know one which is able to solve this kind of problem? (I mean corrupted tables, not religious clients)
>>>
>>>Thank you.
>>>
>>> Héctor
>>I would spend more time fixing the problem than fixing the damage cause by the problem. Does your customer have a UPS? If not, charge him 100$ the first you repair his indexes, 200$ the second time, 400$ the third time, 800$ the fourth time and so on. Either your customer gets smarter, or you get richer.
>
>
>Agree completely! Also make sure if the customer has a UPS on each workstation, server, and router/hub in the system, also make sure the UPSs are WORKING! We've learned not to be suprised anymore when a new client proudly shows us a ups that turns out to be a decade old and completely useless.

My experience is that you MUST replace the batteries every second year. But with today's prices, and the way they mount the batteries making them a nightmare to replace, it's usually cheaper to by new UPSs.