Groups | Search | Server Info | Login | Register
Groups > comp.databases.ms-access > #3850
| From | "Albert D. Kallal" <PleaseNOOOsPAMmkallal@msn.com> |
|---|---|
| Newsgroups | comp.databases.ms-access |
| References | <jg46v7$akn$1@dont-email.me> |
| Subject | Re: Anyone have EXPERIENCE in converting 32 bit Access to 64 bit? |
| Message-ID | <2LhVq.4224$DZ1.2921@newsfe07.iad> (permalink) |
| Date | 2012-01-29 13:12 -0700 |
"BobAlston" wrote in message news:jg46v7$akn$1@dont-email.me... >Anyone have EXPERIENCE in converting 32 bit Access to 64 bit? As a general rule, it is strongly recommend that you stick to Access 32. There is little if any reason I can think of jumping to use Access x64. The list of downsides is quite large when you move to x64. Most if not all of any windows API code has to be modified to use the windows 64 bit version. If you use Access x32 even on 64 bit os, no change is required. If one is using any external ActiveX (com objects) that are x32, then you have to find an equivalent 64 bit version. With treeview, listview, and the Calendar, all of these have quite common been used over the years in Access applications. However, NONE of them can be used with Access x64 (you have to find x64 versions of these controls, and for the most part none exist!). So for applications that use treeview, then Access x64 cannot be used. Last but not least, x64 of Access cannot automate say Outlook 2007 or ANY previous version of word. In other words, you cannot mix and max the "bit size" of applications. So if you deploy the Access x64 runtime on a machine with any previous version of office, you not be able to automate Word, Excel, Outlook etc. Last but not least, be aware that an accDE compiled with Access x64 cannot be consumed and used by Access x32 (even including the same release and office version of Access). In other words you now have to maintain and distribute two versions of an accDE if you going to support Access x64. This requirement does not exist for accDB since the VBA source code is included and thus on-demand compiles can occur. However, the VBA code will have to include switches for API calls etc. and of course one cannot use the x64 bit wide new variable types we have in the x64 bit version of Access in the x32 version. Since there are VERY few reasons to use Access x64, it best to use and stick to using Access x32, and that is even the case for office 2010. -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada Pleasenospam_kallal@msn.com
Back to comp.databases.ms-access | Previous | Next — Previous in thread | Find similar
Anyone have EXPERIENCE in converting 32 bit Access to 64 bit? BobAlston <bobalston9@yahoo.com> - 2012-01-29 13:34 -0600 Re: Anyone have EXPERIENCE in converting 32 bit Access to 64 bit? "Albert D. Kallal" <PleaseNOOOsPAMmkallal@msn.com> - 2012-01-29 13:12 -0700
csiph-web