Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Access 2010 32-bit runtime installation error with 64-bit office
2,946 views
Skip to first unread message
PW
May 5, 2012, 2:31:21 PM5/5/12
to
Hi,
How do I resolve this??!!
We have a client trying to install our runtime application created
with Access 2010 32-bit and she is receiving this error:
'You cannot install the 32-bit version of Office 2010 because you have
64-bit Office products installed. These 64-bit products are not
supported with 32-bit installations: Microsoft Office Publisher 2010;
Microsoft Office Single Image 2010. If you want to install 32-bit
Office 2010, you must uninstall all 64-bit Office products first, and
then run setup.exe in the x86 folder. If you want to install 64-bit
Office 2010, close this Setup program, and then either go to the x64
folder at the root of your CD or DVD and run setup.exe, or get the
64-bit Office 2010 from the same place you purchased 32-bit Office
2010.'
-paul
How do I resolve this??!!
We have a client trying to install our runtime application created
with Access 2010 32-bit and she is receiving this error:
'You cannot install the 32-bit version of Office 2010 because you have
64-bit Office products installed. These 64-bit products are not
supported with 32-bit installations: Microsoft Office Publisher 2010;
Microsoft Office Single Image 2010. If you want to install 32-bit
Office 2010, you must uninstall all 64-bit Office products first, and
then run setup.exe in the x86 folder. If you want to install 64-bit
Office 2010, close this Setup program, and then either go to the x64
folder at the root of your CD or DVD and run setup.exe, or get the
64-bit Office 2010 from the same place you purchased 32-bit Office
2010.'
-paul
PW
May 6, 2012, 12:30:09 AM5/6/12
to
I forgot to say that I am running the 32 bit version of Office on my
PC. I realize that there is a 64-bit Access 2010 runtime but don't
know if that will work for me.
PC. I realize that there is a 64-bit Access 2010 runtime but don't
know if that will work for me.
Patrick Finucane
May 6, 2012, 1:35:59 AM5/6/12
to
when your client already has Office?
Maybe use Google to assist you in finding answers. I looked for
can access 64 bit run 32 bit applications
and got some hits.
Maybe look at one of the links in the hit list to the searth from MS.
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CGwQFjAA&url=http%3A%2F%2Fwindows.microsoft.com%2Fen-us%2Fwindows-vista%2F32-bit-and-64-bit-windows-frequently-asked-questions&ei=NwymT-utApKm8ASli4mVAw&usg=AFQjCNGCvuctNrG2Ov5LbwbUQp81vKNtsA&sig2=tLUFsvau4e1lnFlcdTs0cw,
and read the topic in that page "Can I run 32 bit programs on a 64 bit
computer"
PW
May 6, 2012, 1:26:15 PM5/6/12
to
On Sat, 5 May 2012 22:35:59 -0700 (PDT), Patrick Finucane
<patrickf...@gmail.com> wrote:
>On May 5, 1:31 pm, PW <emailaddyin...@ifIremember.com> wrote:
>> Hi,
>>
>> How do I resolve this??!!
>>
>> We have a client trying to install our runtime application created
>> with Access 2010 32-bit and she is receiving this error:
>>
>> 'You cannot install the 32-bit version of Office 2010 because you have
>> 64-bit Office products installed. These 64-bit products are not
>> supported with 32-bit installations: Microsoft Office Publisher 2010;
>> Microsoft Office Single Image 2010. If you want to install 32-bit
>> Office 2010, you must uninstall all 64-bit Office products first, and
>> then run setup.exe in the x86 folder. If you want to install 64-bit
>> Office 2010, close this Setup program, and then either go to the x64
>> folder at the root of your CD or DVD and run setup.exe, or get the
>> 64-bit Office 2010 from the same place you purchased 32-bit Office
>> 2010.'
>>
>> -paul
>
>Why are you forcing your client to install an Access runtime engine
>when your client already has Office?
>
We distribute an ACCDE (installed from a CD). An icon is created to
<patrickf...@gmail.com> wrote:
>On May 5, 1:31 pm, PW <emailaddyin...@ifIremember.com> wrote:
>> Hi,
>>
>> How do I resolve this??!!
>>
>> We have a client trying to install our runtime application created
>> with Access 2010 32-bit and she is receiving this error:
>>
>> 'You cannot install the 32-bit version of Office 2010 because you have
>> 64-bit Office products installed. These 64-bit products are not
>> supported with 32-bit installations: Microsoft Office Publisher 2010;
>> Microsoft Office Single Image 2010. If you want to install 32-bit
>> Office 2010, you must uninstall all 64-bit Office products first, and
>> then run setup.exe in the x86 folder. If you want to install 64-bit
>> Office 2010, close this Setup program, and then either go to the x64
>> folder at the root of your CD or DVD and run setup.exe, or get the
>> 64-bit Office 2010 from the same place you purchased 32-bit Office
>> 2010.'
>>
>> -paul
>
>Why are you forcing your client to install an Access runtime engine
>when your client already has Office?
>
launch our application.
We don't want clients to have to open up Access, then the ACCDE,....
not professional.
>Maybe use Google to assist you in finding answers. I looked for
> can access 64 bit run 32 bit applications
>and got some hits.
>
>Maybe look at one of the links in the hit list to the searth from MS.
>http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=0CGwQFjAA&url=http%3A%2F%2Fwindows.microsoft.com%2Fen-us%2Fwindows-vista%2F32-bit-and-64-bit-windows-frequently-asked-questions&ei=NwymT-utApKm8ASli4mVAw&usg=AFQjCNGCvuctNrG2Ov5LbwbUQp81vKNtsA&sig2=tLUFsvau4e1lnFlcdTs0cw,
>and read the topic in that page "Can I run 32 bit programs on a 64 bit
>computer"
>
Access 2010 (and Office 2010).
Thanks,
-paulw
Patrick Finucane
May 6, 2012, 3:21:02 PM5/6/12
to
> >and read the topic in that page "Can I run 32 bit programs on a 64 bit
> >computer"
>
> Nothing there Patrick. I am running 64-bit Windows 7 but 32-bit
> Access 2010 (and Office 2010).
>
> Thanks,
>
> -paulw
It's an issue you weren't considering when creating the package. How
> >computer"
>
> Nothing there Patrick. I am running 64-bit Windows 7 but 32-bit
> Access 2010 (and Office 2010).
>
> Thanks,
>
> -paulw
would you know?
But it still seems sucky that the person MUST use your runtime.version
regardless whether or not they have already a full blown version of
office or a simple license for Access. JMO.
Ron Paii
May 7, 2012, 8:11:24 AM5/7/12
to
"PW" <emailad...@ifIremember.com> wrote in message
news:9asaq79s2r9e9n92g...@4ax.com...
1) Support 64 bit office and distribute in both formats.
2) Get your client to reinstall Office using the default 32 bit version.
Microsoft recommends 32 bit unless you need the extra memory 64 bit
supports.
PW
May 7, 2012, 1:04:29 PM5/7/12
to
did not intend that their MS Access ever be used for professional
development. Used to write distributable applications.
-paulw
PW
May 7, 2012, 1:10:17 PM5/7/12
to
version of MS OFFICE???? I deal with these geeks all the time. They
find some person that is basically a handy man of some sort who
pretends to be a professional whatever and suggest that they buy a
64-bit version of MS Office!
-paulw
Ron Paii
May 7, 2012, 4:45:56 PM5/7/12
to
"PW" <emailad...@ifIremember.com> wrote in message
uncheck 32 bit. Microsoft even tells you during the install that they
recommend 32 bit.
PW
May 8, 2012, 7:33:14 PM5/8/12
to
It may come down to this:
http://msdn.microsoft.com/en-us/library/aa384249%28v=vs.85%29.aspx
Unbelievable! I have multiple 32-bit applications running on 64-bit
Windows 7 without a problem. But, not with a MS product.
Thanks.
Access Developer
May 9, 2012, 2:22:53 AM5/9/12
to
You can run multiple 32bit Office components on 64-bit Windows, too; you
just can't mix 32-bit Office and 64-bit Office because of the libraries with
the same names. The software just stumbles all over itself.
I reckon you got some bad advice, but not from Microsoft, I'd guess -- they
are very careful about warning about mixing 32- and 64-bit. Gotta be careful
whose advice you take... sometimes that's so, even if it comes from M'soft.
--
Larry Linson
Microsoft Office Access MVP
Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
"PW" <emailad...@ifIremember.com> wrote in message
news:33bjq7l9043mc32j5...@4ax.com...
just can't mix 32-bit Office and 64-bit Office because of the libraries with
the same names. The software just stumbles all over itself.
I reckon you got some bad advice, but not from Microsoft, I'd guess -- they
are very careful about warning about mixing 32- and 64-bit. Gotta be careful
whose advice you take... sometimes that's so, even if it comes from M'soft.
--
Larry Linson
Microsoft Office Access MVP
Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
"PW" <emailad...@ifIremember.com> wrote in message
PW
May 9, 2012, 11:48:12 AM5/9/12
to
On Wed, 9 May 2012 01:22:53 -0500, "Access Developer"
<accd...@gmail.com> wrote:
>You can run multiple 32bit Office components on 64-bit Windows, too; you
>just can't mix 32-bit Office and 64-bit Office because of the libraries with
>the same names. The software just stumbles all over itself.
>
>I reckon you got some bad advice, but not from Microsoft, I'd guess -- they
>are very careful about warning about mixing 32- and 64-bit. Gotta be careful
>whose advice you take... sometimes that's so, even if it comes from M'soft.
Thanks Larry. It was a client's "IT" guy that decided to install
<accd...@gmail.com> wrote:
>You can run multiple 32bit Office components on 64-bit Windows, too; you
>just can't mix 32-bit Office and 64-bit Office because of the libraries with
>the same names. The software just stumbles all over itself.
>
>I reckon you got some bad advice, but not from Microsoft, I'd guess -- they
>are very careful about warning about mixing 32- and 64-bit. Gotta be careful
>whose advice you take... sometimes that's so, even if it comes from M'soft.
64-bit Office on their computers. At least in our business, some of
these people are pretty scary.
-paul
Ron Paii
May 9, 2012, 1:22:00 PM5/9/12
to
"Access Developer" <accd...@gmail.com> wrote in message
news:a0ugpr...@mid.individual.net...
that needed to reference information in a Jet BE; It can't be done; unless I
install 64-bit office. I ended up adding a linked server on a SQL server,
which is slow but works.
PW
May 9, 2012, 1:43:13 PM5/9/12
to
-paul
PW
May 9, 2012, 1:47:17 PM5/9/12
to
PW
May 9, 2012, 5:34:56 PM5/9/12
to
distribute a 32 bit version application because it will be compatible
with both the 32-bit and 64-bit version of Access and Windows.
Obviously, that is incorrect!
Ron Paii
May 10, 2012, 7:55:54 AM5/10/12
to
"PW" <emailad...@ifIremember.com> wrote in message
compatible. I would test, before release.
PW
May 10, 2012, 12:31:45 PM5/10/12
to
is not compatible with any other 32-bit version of Office
programs....". and "The MDE and ACCDE files, a common way for Access
application developers to distribute solutions and protect their
intellectually property, do not work in the 64-bit version of
Office..."
I will state it again. Microsoft never meant for Access to be used by
any one else but "secretaries".
PW
May 10, 2012, 1:27:20 PM5/10/12
to
On Sat, 05 May 2012 12:31:21 -0600, PW
<emailad...@ifIremember.com> wrote:
<emailad...@ifIremember.com> wrote:
"Microsoft Access MDE/ADE/ACCDE files - Databases that have had their
source code removed (....) cannot be moved between 32-bit and 64-bit
editions of Office 2010. Such databases that are created by using
32-bit Office (any version) can be used only with 32-bit Office, and a
database that is created on 64-bit Office can be used only on 64-bit
Office".
So much for the "intellectually property" that MS referred to in an
earlier post of mine.
Thanks MS!
Ron Paii
May 11, 2012, 8:02:53 AM5/11/12
to
"PW" <emailad...@ifIremember.com> wrote in message
would need to compile in both formats, (ie have 2 workstations, one 32-bit
and the other 64-bit). Really no different then in other programming
environments. The problem with Office and Access/Jet IMO, is they need a new
64-bit library so that 3rd party 64-bit applications can reference the BE
files even if 32-bit Office is installed. BTW, Microsoft does have a 64-bit
Jet download, but it can't be installed with 32-bit Office.
PW
May 11, 2012, 2:49:43 PM5/11/12
to
-paul
Ron Paii
May 11, 2012, 4:17:02 PM5/11/12
to
"PW" <emailad...@ifIremember.com> wrote in message
Douglas J Steele
May 11, 2012, 5:39:00 PM5/11/12
to
No, you could get by with having a 32 bit version of Office in a virtual
machine.
"PW" wrote in message news:knnqq7d5l0iotvl3r...@4ax.com...
machine.
"PW" wrote in message news:knnqq7d5l0iotvl3r...@4ax.com...
PW
May 11, 2012, 5:51:42 PM5/11/12
to
On Fri, 11 May 2012 17:39:00 -0400, "Douglas J Steele"
<NOSPAM_djsteele@NOSPAM_gmail.com> wrote:
>No, you could get by with having a 32 bit version of Office in a virtual
>machine.
Hmmm... Not sure how to do that. I would have a 64-bit version of
<NOSPAM_djsteele@NOSPAM_gmail.com> wrote:
>No, you could get by with having a 32 bit version of Office in a virtual
>machine.
Office in the virtual machine.
Thanks,
-paulw
Access Developer
May 12, 2012, 12:06:32 AM5/12/12
to
"PW" <emailad...@ifIremember.com> wrote
>> No, you could get by with having a 32 bit
>> version of Office in a virtual machine.
> Hmmm... Not sure how to do that. I would
> have a 64-bit version of Office in the
> virtual machine.
Because the point is to set up something compatible with the 32-bit version,
_why_ would you install the 64-bit version in the VM? Just wondering.
Larry
>> No, you could get by with having a 32 bit
>> version of Office in a virtual machine.
> Hmmm... Not sure how to do that. I would
> have a 64-bit version of Office in the
> virtual machine.
_why_ would you install the 64-bit version in the VM? Just wondering.
Larry
PW
May 12, 2012, 3:49:55 PM5/12/12
to
compile our 32-bit Access with 64-bit Access on my PC then they would
be able to run it.
-paul
Access Developer
May 12, 2012, 7:01:19 PM5/12/12
to
I'd opt for using 32-bit Access exclusively in creating 32-bit runtime DBs
and 64-bit Access (if forced, under duress) to create 64-bit runtime DBs.
I've been in the software business 'way too long to be optimistic about
compatibility of a drastic (IMNSHO) difference such as that.
--
Larry Linson
Microsoft Office Access MVP
Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
and 64-bit Access (if forced, under duress) to create 64-bit runtime DBs.
I've been in the software business 'way too long to be optimistic about
compatibility of a drastic (IMNSHO) difference such as that.
--
Larry Linson
Microsoft Office Access MVP
Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
"PW" <emailad...@ifIremember.com> wrote in message
news:nkftq7to6u24mierh...@4ax.com...
Albert D. Kallal
May 12, 2012, 9:27:14 PM5/12/12
to
"PW" wrote in message news:l3rnq7p1dmnlo9mic...@4ax.com...
>From Microsoft's website: "Note: The 64-bit version of Office 2010
>is not compatible with any other 32-bit version of Office
>programs....". and "The MDE and ACCDE files, a common way for Access
>application developers to distribute solutions and protect their
>intellectually property, do not work in the 64-bit version of
>Office..."
The above is not correct. If you compile a mde or accDE with Access 64, then
you need access 64 runtime.
If you use a mdb or accDB, the source code is available and thus re-compile
occurs on the fly.
So you can most certainly use a compiled accDE with Access 2010 (x32 or
x64), the only restriction for compiled code is that you use the correct
version of Access x32 or x64.
As noted, this problem does not exist with a mdb or accDB since source code
is available.
I mean, if you compile code to x32, then you need x32 libraries to support
that code.
I mean if you compile code to x64, then you need x64 libraries to support
that code.
how the above works is quite much how all of the computer industry has
worked since the first PC came out.
It would have been really nice if we could install two versions of Excel or
Word from the same version of office, but the problem is those shared
libraries (so spell checker, VBA, VBA editor, JET, fluent UI (ribbon) etc
are all shared among all of the office products. So only one copy of these
"parts" are installed and then shared.
So, only one bit size version of a given version of office can be installed.
However, as noted, you can most certainly use a accDE or mde with x64
runtime, but you have to then compile that accDE with the correct version of
office.
So the above is correct that a compiled x32 accDE cannot be used with Access
x64, but if you create a x64 compiled accDE with Access x64 then it works
fine. And of course you cannot consume the x64 accDE with Access 32. So the
compatibility they are speaking about is WHEN you use different bit size,
not that Access x64 cannot use and create accDE files since it can do this
without problems.
Also, if you do use the x64 version of Access then all and any api's calls
to windows have to be modified since you calling the x64 versions of windows
api's, and not the x32 version or what is called WOW (WINDOWS on windows -
x32 compatibility layer). In fact, this means your memory handles in Access
actually require a 64 bit wide memory variable. So values returned back from
windows can be x64 in length (you can stuff those values into the new var
type called longlong). We also for the first time in Access now have a
pointer data type that is 32 bits in length for the x32 version and 64 bits
in length for the x64 version. If we had this "pointer" data type in the
past then then our windows API code calls could likely be used without
modification for api calls. However we had to use a long variable data type
for API calls to windows and with the x64 version that pointer has to be 64
bits in length.
Note that in Access x64, the long variable data type for compatibility
reasons remains 32 bits, but you can use longlong data type in x64 if you
want to use a x64 bit size variable that can hold really honking big numbers
in that variable.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
PleaseNoS...@msn.com
>From Microsoft's website: "Note: The 64-bit version of Office 2010
>is not compatible with any other 32-bit version of Office
>programs....". and "The MDE and ACCDE files, a common way for Access
>application developers to distribute solutions and protect their
>intellectually property, do not work in the 64-bit version of
>Office..."
you need access 64 runtime.
If you use a mdb or accDB, the source code is available and thus re-compile
occurs on the fly.
So you can most certainly use a compiled accDE with Access 2010 (x32 or
x64), the only restriction for compiled code is that you use the correct
version of Access x32 or x64.
As noted, this problem does not exist with a mdb or accDB since source code
is available.
I mean, if you compile code to x32, then you need x32 libraries to support
that code.
I mean if you compile code to x64, then you need x64 libraries to support
that code.
how the above works is quite much how all of the computer industry has
worked since the first PC came out.
It would have been really nice if we could install two versions of Excel or
Word from the same version of office, but the problem is those shared
libraries (so spell checker, VBA, VBA editor, JET, fluent UI (ribbon) etc
are all shared among all of the office products. So only one copy of these
"parts" are installed and then shared.
So, only one bit size version of a given version of office can be installed.
However, as noted, you can most certainly use a accDE or mde with x64
runtime, but you have to then compile that accDE with the correct version of
office.
So the above is correct that a compiled x32 accDE cannot be used with Access
x64, but if you create a x64 compiled accDE with Access x64 then it works
fine. And of course you cannot consume the x64 accDE with Access 32. So the
compatibility they are speaking about is WHEN you use different bit size,
not that Access x64 cannot use and create accDE files since it can do this
without problems.
Also, if you do use the x64 version of Access then all and any api's calls
to windows have to be modified since you calling the x64 versions of windows
api's, and not the x32 version or what is called WOW (WINDOWS on windows -
x32 compatibility layer). In fact, this means your memory handles in Access
actually require a 64 bit wide memory variable. So values returned back from
windows can be x64 in length (you can stuff those values into the new var
type called longlong). We also for the first time in Access now have a
pointer data type that is 32 bits in length for the x32 version and 64 bits
in length for the x64 version. If we had this "pointer" data type in the
past then then our windows API code calls could likely be used without
modification for api calls. However we had to use a long variable data type
for API calls to windows and with the x64 version that pointer has to be 64
bits in length.
Note that in Access x64, the long variable data type for compatibility
reasons remains 32 bits, but you can use longlong data type in x64 if you
want to use a x64 bit size variable that can hold really honking big numbers
in that variable.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
PleaseNoS...@msn.com
Albert D. Kallal
May 12, 2012, 9:45:05 PM5/12/12
to
"PW" wrote in message news:0e2rq750av1ip151a...@4ax.com...
>On Fri, 11 May 2012 17:39:00 -0400, "Douglas J Steele"
><NOSPAM_djsteele@NOSPAM_gmail.com> wrote:
>>No, you could get by with having a 32 bit version of Office in a virtual
>>machine.
>Hmmm... Not sure how to do that. I would have a 64-bit version of
>Office in the virtual machine.
The free "windows xp mode" or virtual pc mode does not support 64 bit
versions of the OS. (I really wish it did, as this would then be oh so
easy).
I have in the range of 15 VPC's on my computer ranging from DOS 5, windows
3.1, windows 98, vista, many copies of windows xp and even several copies of
windows 7 all running on my dev computer.
I even made a VPC with just Access 2010 runtime for testing.
So virtual computing is to developers as to what word processing is to
personal assistants working in a office.
If office x64 was the norm, then VPC would be most ideal solution.
However, in this case with the reverse? I would setup and use Virtual Box
which is free from Oracle/sun here and supports x64 os:
https://www.virtualbox.org/
I used the above for hosting a SharePoint setup (it also needed x64 os
support).
The only downfall in Virtual Box is you have to install an x64 OS into
Virtual Box where as VPC running "as xp mode" on windows 7 uses the host win
7 license for windows XP. So this is free and great setup since you don't
need to purchase or have an extra copy of windows lying around (nor do you
have to activate it). Unfortunately, no x64 os support exists in VPC.
So Virtual box means a OS install + having to Activate that copy of windows
but it is a free virtual system.
>On Fri, 11 May 2012 17:39:00 -0400, "Douglas J Steele"
><NOSPAM_djsteele@NOSPAM_gmail.com> wrote:
>>No, you could get by with having a 32 bit version of Office in a virtual
>>machine.
>Hmmm... Not sure how to do that. I would have a 64-bit version of
>Office in the virtual machine.
versions of the OS. (I really wish it did, as this would then be oh so
easy).
I have in the range of 15 VPC's on my computer ranging from DOS 5, windows
3.1, windows 98, vista, many copies of windows xp and even several copies of
windows 7 all running on my dev computer.
I even made a VPC with just Access 2010 runtime for testing.
So virtual computing is to developers as to what word processing is to
personal assistants working in a office.
If office x64 was the norm, then VPC would be most ideal solution.
However, in this case with the reverse? I would setup and use Virtual Box
which is free from Oracle/sun here and supports x64 os:
https://www.virtualbox.org/
I used the above for hosting a SharePoint setup (it also needed x64 os
support).
The only downfall in Virtual Box is you have to install an x64 OS into
Virtual Box where as VPC running "as xp mode" on windows 7 uses the host win
7 license for windows XP. So this is free and great setup since you don't
need to purchase or have an extra copy of windows lying around (nor do you
have to activate it). Unfortunately, no x64 os support exists in VPC.
So Virtual box means a OS install + having to Activate that copy of windows
but it is a free virtual system.
PW
May 14, 2012, 12:12:49 AM5/14/12
to
On Sat, 12 May 2012 19:27:14 -0600, "Albert D. Kallal"
<PleaseNOS...@msn.com> wrote:
>"PW" wrote in message news:l3rnq7p1dmnlo9mic...@4ax.com...
>
>>From Microsoft's website: "Note: The 64-bit version of Office 2010
>>is not compatible with any other 32-bit version of Office
>>programs....". and "The MDE and ACCDE files, a common way for Access
>>application developers to distribute solutions and protect their
>>intellectually property, do not work in the 64-bit version of
>>Office..."
>
>
>The above is not correct. If you compile a mde or accDE with Access 64, then
>you need access 64 runtime.
>
>If you use a mdb or accDB, the source code is available and thus re-compile
>occurs on the fly.
>
>So you can most certainly use a compiled accDE with Access 2010 (x32 or
>x64), the only restriction for compiled code is that you use the correct
>version of Access x32 or x64.
That is the restriction Albert. I do not want our clients or anyone
<PleaseNOS...@msn.com> wrote:
>"PW" wrote in message news:l3rnq7p1dmnlo9mic...@4ax.com...
>
>>From Microsoft's website: "Note: The 64-bit version of Office 2010
>>is not compatible with any other 32-bit version of Office
>>programs....". and "The MDE and ACCDE files, a common way for Access
>>application developers to distribute solutions and protect their
>>intellectually property, do not work in the 64-bit version of
>>Office..."
>
>
>The above is not correct. If you compile a mde or accDE with Access 64, then
>you need access 64 runtime.
>
>If you use a mdb or accDB, the source code is available and thus re-compile
>occurs on the fly.
>
>So you can most certainly use a compiled accDE with Access 2010 (x32 or
>x64), the only restriction for compiled code is that you use the correct
>version of Access x32 or x64.
else but us to have our source code. I create an ACCDE and distribute
it on CD (including the Access runtime) with the basic setup program.
-paul
PW
May 14, 2012, 12:22:29 AM5/14/12
to
>"PW" wrote in message news:l3rnq7p1dmnlo9mic...@4ax.com...
>
>>From Microsoft's website: "Note: The 64-bit version of Office 2010
>>is not compatible with any other 32-bit version of Office
>>programs....". and "The MDE and ACCDE files, a common way for Access
>>application developers to distribute solutions and protect their
>>intellectually property, do not work in the 64-bit version of
>>Office..."
>
>
>The above is not correct. If you compile a mde or accDE with Access 64, then
>you need access 64 runtime.
>
>If you use a mdb or accDB, the source code is available and thus re-compile
>occurs on the fly.
>
>So you can most certainly use a compiled accDE with Access 2010 (x32 or
>x64), the only restriction for compiled code is that you use the correct
>version of Access x32 or x64.
I only have one PC, and it's Win7 64-bit but Office 2010 is 32-bit. I
>
>>From Microsoft's website: "Note: The 64-bit version of Office 2010
>>is not compatible with any other 32-bit version of Office
>>programs....". and "The MDE and ACCDE files, a common way for Access
>>application developers to distribute solutions and protect their
>>intellectually property, do not work in the 64-bit version of
>>Office..."
>
>
>The above is not correct. If you compile a mde or accDE with Access 64, then
>you need access 64 runtime.
>
>If you use a mdb or accDB, the source code is available and thus re-compile
>occurs on the fly.
>
>So you can most certainly use a compiled accDE with Access 2010 (x32 or
>x64), the only restriction for compiled code is that you use the correct
>version of Access x32 or x64.
can not run both on the same PC.
Do you know of a service that I can send my 2010 code to that will do
this for me? We only have one client so far that had someone install
the 64-bit version of MS Office (also Access) 2010. I assume this will
happen again.
-paul
Albert D. Kallal
May 14, 2012, 12:59:28 AM5/14/12
to
"PW" wrote in message news:nq11r7ltqi194c9bp...@4ax.com...
>I only have one PC, and it's Win7 64-bit but Office 2010 is 32-bit. I
>can not run both on the same PC.
>Do you know of a service that I can send my 2010 code to that will do
>this for me? We only have one client so far that had someone install
>the 64-bit version of MS Office (also Access) 2010. I assume this will
>happen again.
>
>-paul
Hum, no not really.
As noted, do take a quick read of my other response here.
if you see my other post, one way would be to download and install Virtual
box.
You would then have to install a x64 os into that virtual system (windows 7
likely the best bet). So this is a bit of work. However, if you do this
install while you do other tasks, then it not so bad and you not tying up
your computer. Give that Virtual box one cpu and 1 gig of ram and that
should more then suffice for hardware requirements.
You then simply install office x64 into that virtual system you setup.
So you would then simply copy your application to that session and create
the accde. So you don't need an extra computer, but you will have to setup
one as "virtual".
As noted, you have to modify any windows API's code you have in Access. So
if you use the api for sleep, or even the common used filedialog api, that
code will have to be changed. There is some compiler switches you can use to
make your code compatible for both x32 and x64 so you at least only have to
maintain one source code copy.
>I only have one PC, and it's Win7 64-bit but Office 2010 is 32-bit. I
>can not run both on the same PC.
>Do you know of a service that I can send my 2010 code to that will do
>this for me? We only have one client so far that had someone install
>the 64-bit version of MS Office (also Access) 2010. I assume this will
>happen again.
>
>-paul
As noted, do take a quick read of my other response here.
if you see my other post, one way would be to download and install Virtual
box.
You would then have to install a x64 os into that virtual system (windows 7
likely the best bet). So this is a bit of work. However, if you do this
install while you do other tasks, then it not so bad and you not tying up
your computer. Give that Virtual box one cpu and 1 gig of ram and that
should more then suffice for hardware requirements.
You then simply install office x64 into that virtual system you setup.
So you would then simply copy your application to that session and create
the accde. So you don't need an extra computer, but you will have to setup
one as "virtual".
As noted, you have to modify any windows API's code you have in Access. So
if you use the api for sleep, or even the common used filedialog api, that
code will have to be changed. There is some compiler switches you can use to
make your code compatible for both x32 and x64 so you at least only have to
maintain one source code copy.
Access Developer
May 14, 2012, 1:36:52 AM5/14/12
to
Interesting, isn't it? For years, the strong point of Access was the
simplicity and ease with which casual users could become sufficiently
skilled to create useful personal and business applications. In recent
years, there've been few or no changes to enhance that strong point, but
only ones aimed at addressing issues that were already
sufficiently-addressed by other software (much of it from Microsoft, also),
and adding nothing but complexity to Access (as witness this whole
exchange).
Does anyone here think that the 64-bit version of Access is "better" in any
way than the 32-bit version... or was it just released because of marketing
hype like DAPs and some other "wonderful new features"? If it doesn't (yet)
have any advances, maybe release should have been delayed until it does?
--
Larry
simplicity and ease with which casual users could become sufficiently
skilled to create useful personal and business applications. In recent
years, there've been few or no changes to enhance that strong point, but
only ones aimed at addressing issues that were already
sufficiently-addressed by other software (much of it from Microsoft, also),
and adding nothing but complexity to Access (as witness this whole
exchange).
Does anyone here think that the 64-bit version of Access is "better" in any
way than the 32-bit version... or was it just released because of marketing
hype like DAPs and some other "wonderful new features"? If it doesn't (yet)
have any advances, maybe release should have been delayed until it does?
--
Larry
rael...@gmail.com
May 14, 2012, 1:45:25 AM5/14/12
to
Rael
Ron Paii
May 14, 2012, 8:05:09 AM5/14/12
to
"PW" <emailad...@ifIremember.com> wrote in message
switch and 64-bit Access? I you are going to develop for customers with
64-bit Office, I would think you would want to test to verify you
application will work when installed.
PW
May 14, 2012, 1:30:48 PM5/14/12
to
On Sat, 12 May 2012 18:01:19 -0500, "Access Developer"
<accd...@gmail.com> wrote:
>I'd opt for using 32-bit Access exclusively in creating 32-bit runtime DBs
>and 64-bit Access (if forced, under duress) to create 64-bit runtime DBs.
>I've been in the software business 'way too long to be optimistic about
>compatibility of a drastic (IMNSHO) difference such as that.
Come to find out the gal said she bought her PC from Best Buy and they
<accd...@gmail.com> wrote:
>I'd opt for using 32-bit Access exclusively in creating 32-bit runtime DBs
>and 64-bit Access (if forced, under duress) to create 64-bit runtime DBs.
>I've been in the software business 'way too long to be optimistic about
>compatibility of a drastic (IMNSHO) difference such as that.
told her that 64-bit everything is the way to go!
PW
May 14, 2012, 1:49:41 PM5/14/12
to
her up to our latest Access 2010 (32-bit) version says she will not
uninstall Office 2010 64-bit and reinstall the 32-bit version because
Best Buy told her that 64-bit everything is the way to go.
I don't think it is worth out trouble to purchase a PC, or create a
virtual box on our PC, another version of Windows 7, Office 64-bit
etc... deal with the work necessary to get our 32-bit version working
with Office 2010 64-bit, just for her. We will warn current and
future customers to stay away from 64-bit Office if they want to use
our software. We are not big enough and do not have the present and
future customer base to deal with this problem that Microsoft created
for us developers.
I remember having to deal with working with clients to remove a font
so that our Access 2003 would install on XP. And service pack issues.
I use other 64-bit software without any problems, but not from MS
(Adobe,...).
Our Access application works great on a Mac with Parallels installed
but will not work now with 64-bit MS Office.
Thanks for everyone's help.
-paulw
PW
May 14, 2012, 7:08:56 PM5/14/12
to
-paul
Access Developer
May 14, 2012, 9:06:55 PM5/14/12
to
If it's not even worth hyping (by the masters of the software hype), why was
it released?
--
Larry Linson
Microsoft Office Access MVP
Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
<rael...@gmail.com> wrote in message
news:12260476.391.1336974325593.JavaMail.geo-discussion-forums@pbcb9...
it released?
--
Larry Linson
Microsoft Office Access MVP
Co-Author, Microsoft Access Small Business Solutions, Wiley 2010
news:12260476.391.1336974325593.JavaMail.geo-discussion-forums@pbcb9...
Access Developer
May 14, 2012, 9:21:39 PM5/14/12
to
Back in the days when I did any business with Best Buy, I dealt with several
sales reps who clearly were working part-time after their schoolday was over
at the local high school. Certainly they were not "authorities" whose
advice on such purchases should be heeded.
Wait a minute... didn't someone say that both the 64- and 32-bit versions
are on the same DVD, and which you load is a matter of just a check-box
during the install process?
Would she be in big trouble at her job if she re-installed or got the
support staff to re-install the 32-bit version?
--
Larry
"PW" <emailad...@ifIremember.com> wrote in message
news:09g2r7d5aa3lmm3pb...@4ax.com...
sales reps who clearly were working part-time after their schoolday was over
at the local high school. Certainly they were not "authorities" whose
advice on such purchases should be heeded.
Wait a minute... didn't someone say that both the 64- and 32-bit versions
are on the same DVD, and which you load is a matter of just a check-box
during the install process?
Would she be in big trouble at her job if she re-installed or got the
support staff to re-install the 32-bit version?
--
Larry
"PW" <emailad...@ifIremember.com> wrote in message
rael...@gmail.com
May 14, 2012, 9:36:00 PM5/14/12
to
As an MVP, you are closer to Microsoft than me, so you're probably better qualified to answer your question. There was a 64bit version of Office 2007 too, but fortunately it didn't cause any issues (because noone knew about it, so didn't install it).
More often than not, unhyped releases are the software vendor's way of getting customers to beta test their software in a production environment. I don't know too many people who are willing to properly beta test software for another company for free. Most just want to get their hands on the software early.
Rael
More often than not, unhyped releases are the software vendor's way of getting customers to beta test their software in a production environment. I don't know too many people who are willing to properly beta test software for another company for free. Most just want to get their hands on the software early.
Rael
PW
May 14, 2012, 10:02:46 PM5/14/12
to
On Mon, 14 May 2012 20:21:39 -0500, "Access Developer"
<accd...@gmail.com> wrote:
>Back in the days when I did any business with Best Buy, I dealt with several
>sales reps who clearly were working part-time after their schoolday was over
>at the local high school. Certainly they were not "authorities" whose
>advice on such purchases should be heeded.
>
>Wait a minute... didn't someone say that both the 64- and 32-bit versions
>are on the same DVD, and which you load is a matter of just a check-box
>during the install process?
>
Yes. I assume the kid at BB did the install for her.
<accd...@gmail.com> wrote:
>Back in the days when I did any business with Best Buy, I dealt with several
>sales reps who clearly were working part-time after their schoolday was over
>at the local high school. Certainly they were not "authorities" whose
>advice on such purchases should be heeded.
>
>Wait a minute... didn't someone say that both the 64- and 32-bit versions
>are on the same DVD, and which you load is a matter of just a check-box
>during the install process?
>
>Would she be in big trouble at her job if she re-installed or got the
>support staff to re-install the 32-bit version?
>
software, as we just told her that we can not do a thing about it. In
fact, I believe the third-party control that we use for our many
calendars (and plays a big part of our software) is also 32-bit only.
What I think Albert said and what the 64-bit chapter says in the A2010
Programmer's Reference says also (not sure who wrote that chapter):
"There is a potentially very significant drawback to using 64-bit
Access2010." Existing 32-bit ActiveX controls... are not compatible
with 64-bit Access2010. There are three possible solutions: Generate
a 64-bit version yourself (if you have the source code -Not!), Contact
the vendor for an updated version (did, but haven't heard back yet),
Search for an alternative solution (there is none that does what we
use, not even close - and many, many hours of my work went into
learning this control).
If so, nothing we can do!
We are not Adobe, etc... how long did it take them to come out with a
64-bit version of Lightroom, etc... Is there a 64-bit version of Flash
out yet? ;-)
Thanks,
-paulw
PW
May 15, 2012, 12:45:31 PM5/15/12
to
On Sat, 05 May 2012 12:31:21 -0600, PW
<emailad...@ifIremember.com> wrote:
>Hi,
>
>How do I resolve this??!!
>
>We have a client trying to install our runtime application created
>with Access 2010 32-bit and she is receiving this error:
>
>'You cannot install the 32-bit version of Office 2010 because you have
>64-bit Office products installed. These 64-bit products are not
>supported with 32-bit installations: Microsoft Office Publisher 2010;
>Microsoft Office Single Image 2010. If you want to install 32-bit
>Office 2010, you must uninstall all 64-bit Office products first, and
>then run setup.exe in the x86 folder. If you want to install 64-bit
>Office 2010, close this Setup program, and then either go to the x64
>folder at the root of your CD or DVD and run setup.exe, or get the
>64-bit Office 2010 from the same place you purchased 32-bit Office
>2010.'
>
>-paul
The third party control that I use for all of our calendars, is 32-bit
<emailad...@ifIremember.com> wrote:
>Hi,
>
>How do I resolve this??!!
>
>We have a client trying to install our runtime application created
>with Access 2010 32-bit and she is receiving this error:
>
>'You cannot install the 32-bit version of Office 2010 because you have
>64-bit Office products installed. These 64-bit products are not
>supported with 32-bit installations: Microsoft Office Publisher 2010;
>Microsoft Office Single Image 2010. If you want to install 32-bit
>Office 2010, you must uninstall all 64-bit Office products first, and
>then run setup.exe in the x86 folder. If you want to install 64-bit
>Office 2010, close this Setup program, and then either go to the x64
>folder at the root of your CD or DVD and run setup.exe, or get the
>64-bit Office 2010 from the same place you purchased 32-bit Office
>2010.'
>
>-paul
only so that ends that!
Thanks everybody for your help.
-paulw
PW
May 15, 2012, 6:33:42 PM5/15/12
to
Office, I will just put in another hard drive and install Win7 64 and
Office 64. Not sure about the license issues though.
Any way, like I said, our third party calendar ActiveX tool is 32-bit
so I can't go there any way (the vendor has no immediate plans to
update their software to 64-bit).
And, we just twisted the "problem" client to go back to 32-bit Office
and she agreed so all is well now (so far).
Thanks Albert and company!
-paul
0 new messages