Steffen,
So that we're talking apples to apples, I've attached a zip file
that includes an experimental version of DBD::ADO (2.4_01), an
Access 2000 mdb (mytest.mdb) with a table called demo that
includes all the different data types, a perl test script
(mytest.pl), various short cut commands, and the results of
mytest.pl (out.txt).
Are you seeing the same results? Also, do you have a pre Jet 4.0
(Access 2000) mdb that you would send me?
Tom
p.s. I'm guessing that the list server will strip the binary file, so
anyone else who would like a copy please email me directly. Also, DO
NOT use this version in production.
On Mon, Nov 26, 2001 at 03:17:32PM +0100, Steffen Goeldner wrote:
> Thomas A. Lowery wrote:
> >
> > > > > BTW: It seems, that the statement handle attributes need the
> > > > > same mapping.
> > > >
> > > > So the Provider does not supply any information on how to support
> > > > data types adVarWChar and adLongVarWChar.
> > >
> > > Perhaps ADO char types already support unicode.
> >
> > I does appear that the Jet driver supports unicode, however it would
>
> That's new in Jet 4.0 (Access 2000), see e.g.:
>
> <http://support.microsoft.com/support/kb/articles/q275/5/61.asp>
>
> > be very helpful if the Provider informed us ... <sigh> In other
> > words, type_info_all has no knowledge of the unicode support because
> > the provider does not list the data types in a call to
> > OpenSchema(adSchemaProviderType).
>
> It does: 130 == adWChar!
> However, it seems that the result of OpenSchema(adSchemaProviderType)
> depends on the provider, but not on the data source. I got the same
> results for an old Access 2.0 (< Jet 4.0) datafile format.
--
Thomas A. Lowery
See DBI/FAQ http://tlowery.hypermart.net
dbd_ado_t_2_4_01.zip
Description: Zip archive
