>>A command like

>>insert into tipdatabase!tiplog (tip_id) values (1.00)

>>seems to work whether the table is open or not. However under some conditions the insert command produces an error that says either row or table buffering must be enabled. What is the condition that might be causing this?
>>
>>Thanks
>
>Don
>
>Do you actually need to put in the dbc name? I mean, you don't, and I wasn't aware that it would work with it, but is it necessary here. What happens if you do just:
>

insert into tiplog (tip_id) values (1.00)

?
>
>Maybe because you do include the dbc this is causing some dbc-based side-effect.

The command is in a stored procedure. The reference to the dbc was included to allow it to work even if the table was not open. I tested your premise by removing the reference to the dbc and substituting code to force it to open and close appropriately. The result is the same. I get an error that says buffering needs to be enabled.