Re: Different table naming between Native Mysql and Mysql ODBC drivers

Frank ,

OK, this option will be welcome and the  compatibility  between 
MYsql_NATIVE , MYsql_JDBC and MYsql_ODBC will profits from it.
After some small tests I am still not sure witch driver to choose.
MYsql_JDBC is the "slowest" and has no other advantages.
MYsql_NATIVE should be the best solution for OO as frontend to MYSQL but 
is still "slower" than ODBC and can  (for the moment) not connect over 
the internet.
MYsql_ODBC is the fastest, works  in all conditions (except  on Franks 
Windows machine :-) and i suppose that this driver has the most 
attention from the MYsql developers ?

Greetz

Fernand
>
>   
>> Can the difference in Table naming between The Native Mysql driver and 
>> the ODBC driver been changed ?
>>
>> the Native connector uses "DatabaseName.TableName"
>>
>> the ODBC uses "TableName".
>>
>> In Forms based on a SQL statement it gives (so far) no problems, but in 
>> Forms where the data point to the "Table" there is a issue !
>>     
>
> Since with the native connector, you can see tables for more than one
> database, omitting the database name would not be possible. Perhaps
> we'll add an option in a later version, to limit the tables to one
> database. In this case, an additional option to completely hide the
> database might be an option.
>
> Ciao
> Frank
>
>