My point is, the Stonefield Database Toolkit does this for a few hundred US dollars. Writing your own reindexing utility for each application you support costs money and time and is likely going to add up to more than you pay for SDT, which many already own.

Your solution is simple, but it requires you to touch it each time you make changes to the structures or indexes. You also have to remember to touch it anytime you make a change to the code for the indexes. SDT has proven code that only requires you to push a button to revalidate the metadata (it handles all the heavy lifting) and distribute the DBC and metadata files with the release. No worries of ever forgetting to make changes in three places (code that uses the indexes, database to add the indexes, and your table class to update the code to handle the indexes). But you have to do this each and every time you make a tweak, and you have to remember to do it. If I took this approach, I would be certain to forget something once and a while, which further costs me time and money.

I'm not judging. We all have our methods and there are tradeoffs that all developers have to choose. I prefer to add people to my team and leverage proven code that I don't have to maintain, support, or write myself in more time.

Rick White Light Computing, Inc.

www.whitelightcomputing.com

-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Gene Wirchenko Sent: Thursday, February 02, 2017 12:33 To: profoxtech@leafe.com Subject: RE: CleverFox Backup

At 15:41 2017-02-01, "Rick Schummer" profox@whitelightcomputing.com wrote:

[snip]

I mean, who writes their own reindexing routine for Visual FoxPro data these days? (rhetorical question)

What is the point here? That it is difficult or simple?

I have an class associated with each table, I instantiate each class at system startup, each class includes an indexing method, and I have a few procedures that use these methods to reindex. To me, it seems rather simple.

[snip]

Sincerely,

Gene Wirchenko

[excessive quoting removed by server]