>
>Almost. It'll trigger error 41 on that line not on the REPLACE. There could be some other differences depending on error. If you just want to catch error 41 than it'll have the same effect. If you want exactly the same effect, replace fpt file with some other file.
The approach with ERROR 41 didn't work. I am calling this stored procedure via OleDb driver which does not support this feature.
When I replaced the .FTP file I get error 111 - "Cannot update the cursor since it is read-only". This is not bad, at least I can trap some error.
But speaking about OleDb, the most frustrating (and upsetting) is that VFPT didn't provide support for TRY/CATCH in OleDb.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
