Jerry,

I would think you could not get around that one. I always reindexed the tables on the clipper side until we got it moved completely over to the VFP app when we did our conversion. Are you recreating the Clipper app in VFP or is it too large and plan to stay with using them both? When you add the data to the Clipper tables thru VFP is it not creating the current indexes used in the Clipper table? Does it corrupt it and hence you need to reindex them? Are you creating new indexes after adding the data? Maybe there is a way to temp store the data in a different format then instead of running a Clipper app to reindex, have the Clipper app run a routinue to pull the data into the clipper table from a different format that will create the indexes on the clipper table correctly without a reindex. Is your main concern getting the data and indexes in and ready to go quickly, or are you trying to get away from running clipper apps in the background altogether?


We have a situation where a VFP9 app updates a Clipper DOS DBF. But after the process is done, the last thing that VFP does is shell out to run a Clipper routine that reindexes the table(s).

We are hoping top be able to avoid this last step and just update the Clipper indexes on the fly.


>Jerry,
>
>What exactly do you mean by update? I did a conversion from clipper tables to VFP and at one time had both applications running on the same tables. I did get corruption on some of the data, but very little (only ftp related). In fact the VFP application we are running now, many years later, still have some older tables in use that were originally used in our Clipper app.