![]() Rather than attempting to answer all of your questions, I'll bite off a chunk. Also, I hope that the above table dispalys properly! There seem to be are a large number of possibly relevant factors. I apologise in advance for the length and messiness of this question. Am I actually restricted to using OLE DB drivers? If not, how do I select ODBC ones?.How do I see / control which version of the import / export wizard I am calling from SSMS?.I presume that they will respectively use 32-bit and 64-bit OLE DB drivers – is this correct? I gather that there are 32-bit and 64-bit versions of the Import and Export wizards.How do I install both 32-bit and 64-bit OLE DB drivers for Office apps (or ODBC drivers for that matter) on the same machine, given that it is impossible to install 32-bit and 64-bit Office versions side by side?.How do I get to see the installed OLE DB drivers and versions on a PC?.That leaves me with the following questions: Presumably the import is using a 64-bit version of the driver on the failing machine, and a 32-bit version on the good one. Personally, I suspect that the problem stems from the OLE DB driver for Excel (or is it an ODBC driver?). I really want to get the failing PC working without having to backgrade the Office version. Although both machines have a 64-bit Windows installation, the working PC is running a 32-bit version of Office whereas the failing PC is running a 64-bit version of Office. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |