Hello Sergey,

There would be little point to set the TABLEPROMPT in the config if it wasn't scoped to the entire project, thus I assumed by them mentioning setting this in the config it was implied it was scoped accordingly.

I set the TABLEPROMPT OFF in the config file and seems to work properly in all but one place. So I set a break point a couple lines before the problem command, and to my surprise SET('TABLEPROMPT') was set to 'ON'.

I havn't had time to run it down, I fixed the problem by just setting it off just before the INSERT INTO. I will put the SET('TABLEPROMPT') in the debugger and set a break on change when I get a chance to find where it's changing.

Bob

>Hi Bob,
>
>>I use the SET TABLEPROMPT OFF to allow me to trap errors if a table cannot be opened instead of having VFP bring up a dialog for the user to pick one (Gasp!). It does not state the scope of this command in the help but it seems to be scoped to the entire project (which seems to be validated by the notation you can set it in the Config.FPW file).
>
>The SET TABLEPROMPT command has global scope. Note, that you can put any SET commnad in the config.fpw regardless of it scope.
>
>>Seems to work as expected MOST of the time. However, on my login form I have an error logger which brings up the file picker dialog on an INSERT INTO command wrapped by a TRY/Catch.
>>
>>If I step through the code just prior, I can see by using SET('TABLEPROMPT') that it is set to ON even though every where elese it shows as OFF. I used the code references tool to make sure I didn't have an accidental reference that did this.
>
>Are you saying that SET TABLEPROMPT OFF saddenly changes to ON on TRY statement?