In the data envirnoment of the Invoice Header form are 16 tables.
The product table is one of them.
There is no links between the tables in the data environment window.
I did not know the data envirnment opened the table, but I'm not surprised - thanks for that info.

The code in the init procedure of the data environment is:

Set Deleted On
SET CENTURY TO 19 ROLLOVER 50
DoDefault()

There is no code in any of the procedures for "Cursor9". That is what gets opened when I right click on the "Product" table and select code.

Does this shed any light?

>Kenneth,
>
>A table has to be open before you can do a SEEK. There are several possibilities on how the table is opened.
>
>Tables can be opened:
>1) In the load method of the form, using the USE command (my preference)
>2) In the Data Environment of the form (right click inside of the form in design mode and choose Data Environment)
>3) Your system may be based on views. Perhaps a view is being opened that has the Product table as the underlying table.
>4) There may be a SELECT statement somewhere that queries the Product table. This would open the table. I guess this SQL Select could be the recordSource for a list box you mentioned.
>
>If your system is using a VIEW to the product table, that would have an impact on how you implement your solution.
>
>If I am missing any other ways the table could be opened, perhaps someone else will fill in the blanks...
>
>>>
>>>Yes, back to that part of the problem.
>>>
>>>Can you show us the code where you open the Product table?
>>
>>That is a very resonable request, but this system is huge and code seems to be hidden everywhere. Combine that with my lack of knowledge and I just don't know. Would the code to open the file have to be in the form or is it possible to open the files before the form is opened?
>>
>>What commands open a table? Does SEEK open the file or do you have to open it then SEEK?
>>
>>The form is the invoice header. There is a listbox that has the detail items displayed. To actually change the detail items you click on a details button.
>>
>>Sorry for the lack of knowledge here.