Hello,
=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD
I am using the 64 bit SPSS v22. I am trying to use the Export to Database feature send my dataset to a table within my 32 bit version of MS Access. The error message that I receive is .......... Driver's ConfigDSN,
ConfigDriver, or ConfigTranslator failed
Errors Found:The specified DSN contains an architecture mismatch between the Driver and Application. How can I resolve this? Thanks, Michelle |
Unfortunately, there may not be any easy
way to resolve this, since the 32-bit Access driver doesn't play well with
64-bit applications. Microsoft has a 64-bit driver, but I don't think you
can install it on a system running the 32-bit version of Access.
Rick Oliver Senior Information Developer IBM Business Analytics (SPSS) E-mail: [hidden email] From: MICHELLE WILSON <[hidden email]> To: [hidden email] Date: 02/24/2015 02:15 PM Subject: SPSS 64bit / MS Access 32bit Driver incompatibility Sent by: "SPSSX(r) Discussion" <[hidden email]> Hello, I am using the 64 bit SPSS v22. I am trying to use the Export to Database feature send my dataset to a table within my 32 bit version of MS Access. The error message that I receive is .......... Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed Errors Found: The specified DSN contains an architecture mismatch between the Driver and Application. How can I resolve this? Thanks, Michelle ===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@... (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
The bitness have to be a match between SPSS and ODBC drivers ie MS Office. There are no workarounds (as far as I know).
On Tuesday, 24 February 2015, Rick Oliver <[hidden email]> wrote: Unfortunately, there may not be any easy way to resolve this, since the 32-bit Access driver doesn't play well with 64-bit applications. Microsoft has a 64-bit driver, but I don't think you can install it on a system running the 32-bit version of Access.===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
In reply to this post by MICHELLE WILSON
Hi Michele If you are going to try to transfer between SPSS and Access using ODBC (which the built-in drivers are), the applications concerned have to be the same bit-width at each end. That is, if you have 32-bit Access, you need 32-bit SPSS; similarly, the 64-bit versions will only talk to other 64-bit applications. So you will need to swap one or other of SPSS or Access to match. If that is not possible in your circumstances, you will have to transfer in other ways - e.g. export as a .csv and import that. Or use some third-party converter like StatTransfer to do the conversion between .sav and .accdb/.mdb (which is probably no more convenient than exporting in one of the intermediate formats like .csv) Regards, Adrian -- Adrian Barnett | "It's always the trombone player" | (Faye Dunaway in 'The Arrangement') Email: [hidden email]
|
Bear in mind the qualifier "using
ODBC". You can transfer
data by using Save As (SAVE TRANSLATE). If it is an output table
you need, you can capture it with OMS and write it to an Excel file.
Jon Peck (no "h") aka Kim Senior Software Engineer, IBM [hidden email] phone: 720-342-5621 From: Adrian Barnett <[hidden email]> To: [hidden email] Date: 02/24/2015 04:09 PM Subject: Re: [SPSSX-L] SPSS 64bit / MS Access 32bit Driver incompatibility Sent by: "SPSSX(r) Discussion" <[hidden email]> Hi Michele If you are going to try to transfer between SPSS and Access using ODBC (which the built-in drivers are), the applications concerned have to be the same bit-width at each end. That is, if you have 32-bit Access, you need 32-bit SPSS; similarly, the 64-bit versions will only talk to other 64-bit applications. So you will need to swap one or other of SPSS or Access to match. If that is not possible in your circumstances, you will have to transfer in other ways - e.g. export as a .csv and import that. Or use some third-party converter like StatTransfer to do the conversion between .sav and .accdb/.mdb (which is probably no more convenient than exporting in one of the intermediate formats like .csv) Regards, Adrian -- Adrian Barnett | "It's always the trombone player" | (Faye Dunaway in 'The Arrangement') Email: [hidden email] From: MICHELLE WILSON <[hidden email]> To: [hidden email] Sent: Wednesday, 25 February 2015, 6:44 Subject: SPSS 64bit / MS Access 32bit Driver incompatibility Hello, I am using the 64 bit SPSS v22. I am trying to use the Export to Database feature send my dataset to a table within my 32 bit version of MS Access. The error message that I receive is .......... Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed Errors Found: The specified DSN contains an architecture mismatch between the Driver and Application. How can I resolve this? Thanks, Michelle ===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@... (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@... (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
In reply to this post by Adrian Barnett
Hello,
=====================
To manage your subscription to SPSSX-L, send a message to
[hidden email] (not to SPSSX-L), with no body text except the
command. To leave the list, send the command
SIGNOFF SPSSX-L
For a list of commands to manage subscriptions, send the command
INFO REFCARD
Thank you all for this excellent feedback. We have several programs developed in which SPSS is importing and exporting data directly from and to Access and SQL Server tables. So I think that we are going to uninstall the 64 bit version of SPSS and install the 32 bit version instead. The machine running spss has a 64 bit processor. If anyone anticipates that there might be issues with this solution, I would welcome the heads up. Thanks, Michelle Date: Tue, 24 Feb 2015 23:08:34 +0000 From: [hidden email] Subject: Re: SPSS 64bit / MS Access 32bit Driver incompatibility To: [hidden email] Hi Michele If you are going to try to transfer between SPSS and Access using ODBC (which the built-in drivers are), the applications concerned have to be the same bit-width at each end. That is, if you have 32-bit Access, you need 32-bit SPSS; similarly, the 64-bit versions will only talk to other 64-bit applications. So you will need to swap one or other of SPSS or Access to match. If that is not possible in your circumstances, you will have to transfer in other ways - e.g. export as a .csv and import that. Or use some third-party converter like StatTransfer to do the conversion between .sav and .accdb/.mdb (which is probably no more convenient than exporting in one of the intermediate formats like .csv) Regards, Adrian -- Adrian Barnett | "It's always the trombone player" | (Faye Dunaway in 'The Arrangement') Email: [hidden email]
|
For exactly the same reason I downgraded (or at least tried) Statistics from 64 to 32 bit the only difficulty I had was with the Python. Specifically I had done some edits in registry to get "Edit with IDLE" to work when right clicking a .py file whilst using 64bit but after I "downgraded" to 32 bit (to match MS office), Statistics and Python worked just fine but I lost the ability to right click .py file and select "Edit with Python". And I tried a gazillion and one things to try getting it to work but not being knowledgeable in it all I failed so resorted instead of upgrading MS Office from 32 to 64bit instead.
I guess this will only be applicable if you've already made such modifications to registry as I had. On Wednesday, 25 February 2015, MICHELLE WILSON <[hidden email]> wrote: ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
Administrator
|
In reply to this post by MICHELLE WILSON
Why not acquire/license 64 bit versions of the Access and SQL engines.
If you are running anything requiring huge amounts of memory then going backwards to SPSS 32 bit might be a way of getting bit in the behind. I wonder (Jon would likely know for certain) whether a 32 bit and 64 bit version of SPSS can coexist on a single machine or would that be an accident waiting to happen? --
Please reply to the list and not to my personal email.
Those desiring my consulting or training services please feel free to email me. --- "Nolite dare sanctum canibus neque mittatis margaritas vestras ante porcos ne forte conculcent eas pedibus suis." Cum es damnatorum possederunt porcos iens ut salire off sanguinum cliff in abyssum?" |
In reply to this post by MICHELLE WILSON
Hi Michelle I don't know if this will be an issue for you or not, but 32-bit applications are limited in the amount of memory they can access. It is about 4GB. If your workstation has more then this, your application will still only be able to see 4GB. If you are only ever going to process small datasets (by 'small' in this context, I mean a smallish fraction of 4GB) it probably won't be an issue. The closer the datasets get to 4GB, the less RAM will be available for manipulating the data and the more time will be spent swapping chunks of it between RAM and disk. That is very much slower than when the data can stay in RAM. Sorting is one activity that requires lots of RAM, and it can require two or more times the size of the dataset to do it all in RAM. So if you are likely to be dealing with big datasets, this will impact your work in SPSS. On the Access and Excel side of things, IIRC, the 64-bit versions can handle larger datasets, although even 64-bit Access seems to be limited to 2GB :
A quick check suggests the same limits apply to the 2013 version - MS seem not to have done anything serious to update the internals of Access for along time. Excel seems less limited than clunky old Access:
Anyway, these things may not be issues for the work you do but I mention them in case they are (or might become so in future). Regards, Adrian -- Adrian Barnett | "It's always the trombone player" | (Faye Dunaway in 'The Arrangement') Email: [hidden email]
|
In fact, even on 64-bit Windows most apps
can only address 2GB. Under some circumstances with OS tweaks maybe
3GB but certainly not 4 for a single application. However, most SPSS
operations will use much less than that, because they do not keep the data
in memory. Some time series procedures are an exception as are any
R extension commands you use. (Python extensions generally don't
keep all the data in memory.) Viewer files are in memory and can
get very large if there is a tremendous amount of output.
As for 32 and 64-bit Statistics of the same version, they can probably coexist, although I have never tried that. You would, however, have a conflict in COM operations, in who wins if you double click a file, and probably preference settings. Jon Peck (no "h") aka Kim Senior Software Engineer, IBM [hidden email] phone: 720-342-5621 From: Adrian Barnett <[hidden email]> To: [hidden email] Date: 02/25/2015 04:40 PM Subject: Re: [SPSSX-L] SPSS 64bit / MS Access 32bit Driver incompatibility Sent by: "SPSSX(r) Discussion" <[hidden email]> Hi Michelle I don't know if this will be an issue for you or not, but 32-bit applications are limited in the amount of memory they can access. It is about 4GB. If your workstation has more then this, your application will still only be able to see 4GB. If you are only ever going to process small datasets (by 'small' in this context, I mean a smallish fraction of 4GB) it probably won't be an issue. The closer the datasets get to 4GB, the less RAM will be available for manipulating the data and the more time will be spent swapping chunks of it between RAM and disk. That is very much slower than when the data can stay in RAM. Sorting is one activity that requires lots of RAM, and it can require two or more times the size of the dataset to do it all in RAM. So if you are likely to be dealing with big datasets, this will impact your work in SPSS. On the Access and Excel side of things, IIRC, the 64-bit versions can handle larger datasets, although even 64-bit Access seems to be limited to 2GB : Access 2010 specifications
A quick check suggests the same limits apply to the 2013 version - MS seem not to have done anything serious to update the internals of Access for along time. Excel seems less limited than clunky old Access: Excel specifications and limits
Anyway, these things may not be issues for the work you do but I mention them in case they are (or might become so in future). Regards, Adrian -- Adrian Barnett | "It's always the trombone player" | (Faye Dunaway in 'The Arrangement') Email: [hidden email] From: MICHELLE WILSON <[hidden email]> To: [hidden email] Sent: Thursday, 26 February 2015, 4:15 Subject: Re: SPSS 64bit / MS Access 32bit Driver incompatibility Hello, Thank you all for this excellent feedback. We have several programs developed in which SPSS is importing and exporting data directly from and to Access and SQL Server tables. So I think that we are going to uninstall the 64 bit version of SPSS and install the 32 bit version instead. The machine running spss has a 64 bit processor. If anyone anticipates that there might be issues with this solution, I would welcome the heads up. Thanks, Michelle Date: Tue, 24 Feb 2015 23:08:34 +0000 From: [hidden email] Subject: Re: SPSS 64bit / MS Access 32bit Driver incompatibility To: [hidden email] Hi Michele If you are going to try to transfer between SPSS and Access using ODBC (which the built-in drivers are), the applications concerned have to be the same bit-width at each end. That is, if you have 32-bit Access, you need 32-bit SPSS; similarly, the 64-bit versions will only talk to other 64-bit applications. So you will need to swap one or other of SPSS or Access to match. If that is not possible in your circumstances, you will have to transfer in other ways - e.g. export as a .csv and import that. Or use some third-party converter like StatTransfer to do the conversion between .sav and .accdb/.mdb (which is probably no more convenient than exporting in one of the intermediate formats like .csv) Regards, Adrian -- Adrian Barnett | "It's always the trombone player" | (Faye Dunaway in 'The Arrangement') Email: [hidden email] From: MICHELLE WILSON <[hidden email]> To: [hidden email] Sent: Wednesday, 25 February 2015, 6:44 Subject: SPSS 64bit / MS Access 32bit Driver incompatibility Hello, I am using the 64 bit SPSS v22. I am trying to use the Export to Database feature send my dataset to a table within my 32 bit version of MS Access. The error message that I receive is .......... Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed Errors Found: The specified DSN contains an architecture mismatch between the Driver and Application. How can I resolve this? Thanks, Michelle ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to LISTSERV@... (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD ===================== To manage your subscription to SPSSX-L, send a message to [hidden email] (not to SPSSX-L), with no body text except the command. To leave the list, send the command SIGNOFF SPSSX-L For a list of commands to manage subscriptions, send the command INFO REFCARD |
A quote from SPSS technical support from a historical log I submitted: "Thank you for contacting IBM Technical Support. Unfortunatly, you cannot install both the 32 bit and 64 bit SPSS statsitics of the same version on one windows system.You're right about the ODBC connections between applications. Both applications needs to have the same bitness when using ODBC." On 25 February 2015 at 23:58, Jon K Peck <[hidden email]> wrote: In fact, even on 64-bit Windows most apps can only address 2GB. Under some circumstances with OS tweaks maybe 3GB but certainly not 4 for a single application. However, most SPSS operations will use much less than that, because they do not keep the data in memory. Some time series procedures are an exception as are any R extension commands you use. (Python extensions generally don't keep all the data in memory.) Viewer files are in memory and can get very large if there is a tremendous amount of output. |
Free forum by Nabble | Edit this page |