I am working with old FoxPro 2.6 tables to do archiving of old record (Job Numbers) and am working hard to work through or around these limitations with a DBC and Views.

The table with which I have a problem is one that does not have a unique key. Of course, when you do a SQL Update (check box on Update Criteria tabbed-page), then VFP squawks at you saying that you don't have a unique key. Well, the users aren't going to like the OK/Help Error Dialogue they get for each non-unique key.

I am using Local Parameterized Views. I even added a new field called cRecNo that I updated in my Form Load event, in order to have a unique field, but with 600k+ records, this can be a little too heavy. I removed the cRecNo field, which I had indexed.

I am working separate from an accounting system. I need to work independently of the accounting system and not make mods to it. Unfortunately for me, this presents me with almost no alternatives other than to resort to coding and not using any parameterized views.

Any ideas on this situation? I hoped I explained this clearly enough.