Jozef;

There are a number of things that can be done to minimize data corruption of dbf tables. In general things to consider:

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






>Be so kind and inform VFP team how to prevent dbf’s from having serious problems, please. (especcialy on Novel Networks and in peer to peer environment). Thanks in advance.
>
>
>>
>>I know how to “prevent” dbf’s from having serious problems or repair tables if necessary and have done this professionally. If I used MSDE as a solution for a client I would be concerned about how to respond to a “crash and burn”.
>>
>>
>>Tom
>>
>>
>>
>>>Hi Hugh,
>>>
>>>I my my opinion it all boils down to requirements. If I know up front that the app will be a one or two person app and that the 2GB limit of MSDE will never be an issue - then my choice will be MSDE.
>>>
>>>As far as considering it arrogant to assume that I am making the right decision on my customers behalf ... In my experience, what enables me to retain and pursue new customers is providing them with systems that work as advertised and meet their requirements. Most don't care or have never heard of VFP or MSDE - they just want their systems to meet their needs and be reliable.
>>>
>>>Of course, that can be done using VFP as a back-end - but my preference, based on my experience is to use MSDE where applicable.
>>>
>>>Al
>>>
>>>
>>>>Hi Allan.
>>>>
>>>>While there are downsides to any software product/project, I think it's particulary important to let your paying customers know that you are running your application on top of a shareware/crippleware data engine (which is exactly what MSDE is).
>>>>
>>>>To some degree I would mitigate that opinion for shrinkwrapped applications (over custom designed software applications) but in general I think the customer should be apprised of the facts.
>>>>
>>>>I would consider it arrogant to just assume that you are making the right decision on your customer's behalf.
>>>>
>>>>Would you not agree?
>>>>
>>>>Hugh