PHWinfo - Afficher un message

09/10/2007, 23h42

On 9 Ott, 18:38, Smitty <marksmith...@hotmail.com> wrote:
.... am getting this error now when trying to connect:
> "Could not retrieve OleDB Data Types info from (schema not
> supported)Could not retrieve information about OledDB data types
> from" Thanks again for your - Nascondi testo tra virgolette -
>

Dear Mark,

I had the test done. Here are the findings.

First of all the solution:
---------------------------------------------------------------------------------
1. Download the NEW release: http://www.datatime.eu/download.aspx
2. Download this driver: http://www.datatime.eu/public/MyOLEDB.exe
[ it's a local copy of MyOLEDB 3.00 ]

If you have done a connection to your MySQL, remove it and
make sure
you will NOT use it with the new version of DataTime. Make
a NEW one.

----------------------------------------------------------------

Let me know if this is working for you ! Thank you.

Here is what we found:

1. First of all, there was a bug in DataTime related to MySQL.
But this was not the reason
of your error message. It would just prevent the use of the
old driver MyOLEDB 3.00
Actually it was not expected this bug to be there. It was
probably introduced in one of the
latest revision by one of newer programmers. We have fixed
it now.

2. The provider myoledb-3.9.6.msi that can be found on the
download page seems to have major issues.
It does not support the .NET Oledbschemaguid class. So it's
practically unusable for our purpose
or on the .NET framework.

Strangely, the older version of the provider MyOLEDB 3.00
had this support got [almost] right
therefore you need to use it.
I said "almost" because, strangely, it has in all string an
additional Null char which we remove programmatically
[you can still see it in the display of the
OleDBSchemaGUIDs]
(the above mentioned bug was that this bug removal had been
removed !! ).

========= TO MYSQL USERS ==========

Now the point become: why the newer MyOLEDB is no more
working with .NET ??
Is anyone here that can respond ?

And please, if you fix it, as I hope, make sure to remove
that additional Null char in all the Guid strings. Please !

You can use the DataTime OLEDB scanner to check the Oled
Driver. We have used it will all the commercial drivers
available on the market, and all the serious driver pass
perfectly our scanning. So Mysql should also :-)

-P

09/10/2007, 23h42	#11
pamela fluente Messages: n/a Hébergeur:	Re: Capturing a Schema On 9 Ott, 18:38, Smitty <marksmith...@hotmail.com> wrote: .... am getting this error now when trying to connect: > "Could not retrieve OleDB Data Types info from (schema not > supported)Could not retrieve information about OledDB data types > from" Thanks again for your - Nascondi testo tra virgolette - > Dear Mark, I had the test done. Here are the findings. First of all the solution: --------------------------------------------------------------------------------- 1. Download the NEW release: http://www.datatime.eu/download.aspx 2. Download this driver: http://www.datatime.eu/public/MyOLEDB.exe [ it's a local copy of MyOLEDB 3.00 ] If you have done a connection to your MySQL, remove it and make sure you will NOT use it with the new version of DataTime. Make a NEW one. ---------------------------------------------------------------- Let me know if this is working for you ! Thank you. Here is what we found: 1. First of all, there was a bug in DataTime related to MySQL. But this was not the reason of your error message. It would just prevent the use of the old driver MyOLEDB 3.00 Actually it was not expected this bug to be there. It was probably introduced in one of the latest revision by one of newer programmers. We have fixed it now. 2. The provider myoledb-3.9.6.msi that can be found on the download page seems to have major issues. It does not support the .NET Oledbschemaguid class. So it's practically unusable for our purpose or on the .NET framework. Strangely, the older version of the provider MyOLEDB 3.00 had this support got [almost] right therefore you need to use it. I said "almost" because, strangely, it has in all string an additional Null char which we remove programmatically [you can still see it in the display of the OleDBSchemaGUIDs] (the above mentioned bug was that this bug removal had been removed !! ). ========= TO MYSQL USERS ========== Now the point become: why the newer MyOLEDB is no more working with .NET ?? Is anyone here that can respond ? And please, if you fix it, as I hope, make sure to remove that additional Null char in all the Guid strings. Please ! You can use the DataTime OLEDB scanner to check the Oled Driver. We have used it will all the commercial drivers available on the market, and all the serious driver pass perfectly our scanning. So Mysql should also :-) -P