Jess,

>>Rebalancing indexes is periodically needed to optimize performance indeed. However, With surrogate incrementing keys this more of a problem that with random generated, or mannually entered intelligent keys because balancing indexes would automaticly occur. This is also needed in other DBMSs, however most provide automatic balancing and/or clustered indexes. In most systems I develop a reindexing routine is a suitable solution.
>
>If your system is running 24 hours a day 7 days a week, you need 2 to 3 hours interruption (or longer depending on the volume of data). I think that's a common problem with ISAM databases.

I don't think if 24*7 is a requirement then a VFP database is not a solid solution. A database server like SQL server is a more steady path.

>We have a Finger Scanning VFP application and it gives us headache because the FPT is regularly being corrupted eventhough there is no technical pc problem.

Do you use binary memo field ? Which codepage you use in the tables ? This might be a cause of your problem. With code page "MACHINE" and using binary memofields I've never encountered any problems, though I must admit that I don't use them very frequently.

>>One question tough, why is the SQL-server version as twice as expensive as the VFP version? Only because of purchasing SQL and licences or is there another factor?
>
>Merely because SQL Server is highly respected DB and it adds value to our application. With Oracle you need high caliber DB Admin but with SQL Server, the developer is enough as long as he knows what he's doing.

>VFP DB needs regular maintenance and no matter how complete your app is e.g. reindexing and packing tools, corruption is always imminent because of technical problems beyond the developer's control. And so, there must be a Monthly or Yearly Retainer's Fee which we do. Now, we would rather choose to have a stable app with stable DB than to have a retaineer's fee at all. Really, it's uncomfortable to be in the site doing file fixing at around 3 A.M.

There are a lot of things you can do about this, however a lot of depends on the nature of your application. Reclycling records and using random generated PK fields help to let your indexes say balanced and keep the tables compact. Table or row buffering with transactions helps to avoid almost all corruption problems i've ever encountered.

Walter,