Mensaje
De
29/09/2006 11:50:08
a
29/09/2006 11:37:44
Environment versions
Environment:
VB 8.0
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
ID de la conversación:
01150471
ID del mensaje:
01158163
Views:
63
Hi,
>>That really would be weird and would imply that the errors are not, as suspected, caused by the processing of overlapping hits. The obvious question - are you sure you're the log entry is written before any other processing is done?
>
>The only think that I can see right now is the fact about the reserved words. In all those SQLs, where errors have been reported, I was able to find reserved words. I adjusted some of them last night. So far, so good, no error has been reported. But, if that is the case, it means the OleDb provider would be really cheap when comes time to tell the reason of the error. Giving all kinds of totally non related errors is not making any sense to me.
I read the parallel thread but I'm not convinced of this - if VFPOLEDB was going to choke on reserved words I'd expect it to happen everytime not just intermittently.
Regards,
Viv
>>That really would be weird and would imply that the errors are not, as suspected, caused by the processing of overlapping hits. The obvious question - are you sure you're the log entry is written before any other processing is done?
>
>The only think that I can see right now is the fact about the reserved words. In all those SQLs, where errors have been reported, I was able to find reserved words. I adjusted some of them last night. So far, so good, no error has been reported. But, if that is the case, it means the OleDb provider would be really cheap when comes time to tell the reason of the error. Giving all kinds of totally non related errors is not making any sense to me.
I read the parallel thread but I'm not convinced of this - if VFPOLEDB was going to choke on reserved words I'd expect it to happen everytime not just intermittently.
Regards,
Viv