Hi Randy,

> I don't have the time to re-engineer the whole app, but I do want to try to reduce the physical size of the files as much as I can.

You don't need to re-engineer the whole application. Often the bottle necks are small things that can quickly get fixed if you find them, such as GO TOP statements on filtered tables. A good way for this is too use FILEMON from http://www.sysinternals.com to monitor disk access. Don't spend a lot with all the lines in great detail, just search for lines where the same DBF file is accessed dozens of lines repeatedly. These are table scans that are the worst performance killers across a network.

If you can't deduct the code line from your actions to find the problematic part, put lines like this in the code:

=FILE("procedure whatever #1")

These FILE statements appear in the FILEMON log so that you can search for them. Obviously, any file activity between two markers in the log file maps to the lines that are executed between the two FILE() statements.