>Hello!
>I have been looking for solution to the following problem.
>
>My company uses a FoxPro 2.6 application with
>260 tables,
>2600 fields,
>550 indexes.
>
>The application has a custom built-in data dictionary and a procedure for data validation. The procedure checks the physical tables against the dictionary. It takes 2 minutes on a fast PC with the files
>installed locally to validate the entire database.
>
>We intend to start running this procedure on every client application
>start-up, but 2 mins is far too long. How this problem can be remedied?

Do you really need to run this every time on all the tables? Why not make another table where you'll write the time a table was last checked, and then make some kind of a schedule which will make sure all the tables are checked at regular intervals, but not all the tables every time.

If the "table checking" means indexing a table, I've taken a different approach: I have a procedure which opens the tables, and if it reports index or memo file errors, then the function closes all and runs the indexer routine. If you'd like to see the code, e-mail me.