Sorry to mislead you. I'm traveling and don't have the source code for that app so was describing what I remember. When I was able to set up a Citrix connection and download the source from their network, I confirmed that the process doesn't pack any tables; it copies and renames them and has since the app was moved to VFP3. Other than that though, this process has run largely unmodified since it was originally written in FoxPro LAN 1.0 beta.

In this situation, the workstation and the server froze on the first query. Even if there had been a pack, the process didn't get that far. The first thing the client did after the server was brought back up was reindex the tables. Then they attempted to work normally the following day, adding new records and editing the remaining memo text. Throughout the day users began to report certain text entries were missing from the memo fields in some records. That is when they called me. I didn't attempt dSalvage because so much had happened since the initial problem. There is a backup made at the point where they first called me so I will try your suggestions. Thanks.

Your comments raise an important point. Many times clients move legacy apps to new operating systems, both workstation and server. Is there a repository of information regarding specific problems, issues or even configuration requirements for various OS? I've observed several oddities in this and another VFP app (written by someone else) since the move to Win2K about 10 months ago that make me wonder whether there aren't some real incompatibilities. On a couple of occasions, users have received "record out of range" errors in various tables. Another time, a block of newly added records simply disappeared; records before and after were perfectly intact. The PK is incremented from a stored value and one was mysteriously incremented by 632 when no new records had been created. Both of these applications ran on the Novell server for many years without problems. Neither the IT people nor I can find obvious causes and must assume a general incompatibility between 2.x data and NT servers. I'm trusting that most of these issues will go away when the SQL Server version of the app is deployed. But can I be sure?