Hi Carlos

Thks for posting that thing on mySql site. I did not have realy time on friday to pursue further 'hunt' on this.
Anyways I am planning to use mySql as plan-b for smaller implementations. Main problem here was actually - Oracle!
Where I came across strange problem with dirty buffers on buffered remote views where it should not have one.
I was getting error 1585 (like record contention in shared table scenario) when I was actually running single datasession
having remote view open. Completely strange.

Then I started trying other ODBC-Drivers/Databases one by one, to distinguish where/what actually have problem. Was it my architecture/model or it has something to do with VFP9, or Oracle/driver...
Now real jawbreaker is that my prototype woked just fine with VFP.(o)dbc as backend.

Monday will be defenetely 'action packed' in testing this whole thing.

Thks++
Sergio



>>Perhaps 5.1 driver is still 'young' ;
>>They will fix that driver eventually, til then 3.5.1 will do the job :).
>>
>>I was actually afraid that it has something to do with VFP9, so I got kind of 'relieved' when it worked just fine with older driver.
>>
>>
>>
>>Thank you guys
>>Sergio
>>
>
>This bug has already been reported in the MySql bug database, I have updated the bug entry with new information, maybe this will get fixed soon:
>
>http://bugs.mysql.com/bug.php?id=35067
>
>Notice what happens to the Select statement logged by MySQL in myodbc.sql when you turn debug on, near the WHERE clause when you use a parametrized view in VFP:
>
>WHERE Stock.idcaja = ( _latin1'02DG0PQ0LQ' )
>
>The same remote view with a fixed value instead of a variable turns out as:
>
>WHERE Stock.idcaja = ( '02DG0PQ0LQ' )
>
>So I guess that _latin1 thing is the root of the problem.
>
>By the way, "They will fix that driver eventually" but only if someone reports the bug and can provide information about it, otherwise, it will never get fixed, more so if we talk about Visual FoxPro, I guess they don´t even have a VFP programmer.
>
>This bug http://bugs.mysql.com/bug.php?id=31968 is from OCT 2007, it finally got fixed in APR 2008: http://bugs.mysql.com/bug.php?id=35581 after I lobbyed for it.
>
>Carlos Alloatti