Microsoft.ACE.OLEDB.12.0 - BUG

S

Sven Pran

I have discovered a disturbing bug that took me lots of time to circumvent:

In an excel workbook I have a named range defined as $A:$J and I need to
process this using ADO.

Originally I used the Jet engine and had Extended Properties=Excel 8.0, this
worked with no problems. Then with my new Vista system I have Office 2007 so
I installed ACE and upgraded my workbook to excel 2007 (and of course set
Extended Properties=Excel 12.0). Everything was fine.

For compatibility reasons I also verified that ACE could work with my
unconverted workbooks, but alas - it did not!

My investigations eventually revealed that ACE (with Extended
Properties=Excel 8.0) would only access my named range in the unconverted
workbook after I changed the definition to (for instance) $A$1:$J$300

I have no idea if this is the best place to report such a bug, but I know of
no better place.

regards Sven
 
B

Bob Buckland ?:-\)

Hi Sven,

You may want to also post this in the MS Access discussion group to see if folks there are familiar with the differences between JET
and ACE in this regard, or if it's an Excel limitation.

There are some odd things that happen when linking between Word 2007 and Excel 2007 vs Excel 2003 as well, so it's not always easy
to determine which app needs to be addressed for a resolution.

==============
I have discovered a disturbing bug that took me lots of time to circumvent:

In an excel workbook I have a named range defined as $A:$J and I need to
process this using ADO.

Originally I used the Jet engine and had Extended Properties=Excel 8.0, this
worked with no problems. Then with my new Vista system I have Office 2007 so
I installed ACE and upgraded my workbook to excel 2007 (and of course set
Extended Properties=Excel 12.0). Everything was fine.

For compatibility reasons I also verified that ACE could work with my
unconverted workbooks, but alas - it did not!

My investigations eventually revealed that ACE (with Extended
Properties=Excel 8.0) would only access my named range in the unconverted
workbook after I changed the definition to (for instance) $A$1:$J$300

I have no idea if this is the best place to report such a bug, but I know of
no better place.

regards Sven <<
--
Please let us know if this has helped,

Bob Buckland ?:)
MS Office System Products MVP

LINKS
A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.access
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.access

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com
 
S

Sven Pran

Hi,
well, this is actually not at all relevant when connecting to ACCESS, only
when connecting to EXCEL.

I am now deliberatly cross-posting to an excel group, my apologies in
advance if anybody feels this to be against "netiquette".

regards Sven
 
Top