Jim,

I checked my index key's definition and it's 135 characters long.

I am now wondering if this could be a buffering problem.

I start out with my MergeList table empty
I open a view based on the MergeList table
I INSERT my first record
I INSERT my second record, then when I either try to insert the next record or move to a different record in the view, I get the error message.

Could this be because with each row change the view is trying to insert all of it's records into the table? Is the INSERT (or row change), forcing a TableUpdate?

BTW - I after all the above, and reading your message,
I went in to the MergeList table added a field called PrimaryKey (Character 200) and set it's default value to that long compound command I was using for my index expression. Then I set the PrimaryKey field to be my PRIMARY index.

Then I updated my views and re-ran my program. Now everything works fine.

Each time I hit the INSERT command, not only did the view recieve new data, but the table was updated with the latest unsaved entry prior to the new information being inserted. I did not think the table would be updated prior to each INSERT...but it was....I thought it would wait until I closed the view...oh well.

--------------------
>Richard,
>
>Yes there is a limit to key expression length.
>
>Maximum # of bytes per index key in a compact index = 240
>
>I would suggest that you add one new field to the table named TablePK, make it integer and assign a unique number for each insert. Control the duplicate file names programatically and forget about the error you are now getting. Make the TablePK field the primary index and make the other one a regular index.