64 bit machines

ajetrumpet

Banned
Local time
Today, 17:01
Joined
Jun 22, 2007
Messages
5,638
all,

does anyone have experience installing a program on a 64 bit machine? When i package one of our solutions, it throws the folders and files into PROGRAM FILES. But, on MY 64 bit comp, the default programs file folder is PROGRAM FILES (x64). that will not work the way I've packaged it. Is there any easy solution around this? Other than correcting the code and checking for that folder, then changing all of the code to work right? That would really be a hassle.

I'm thinking that it would just be easier to specify that my programs are not compatible with 64 bit machines. Any takers on advice here?
 
I would advise not ‘hard coding’ paths or the like in more than one place.

Use either a public constant or store the path in a table.
If all you’re after is the path to Access then use: -

SysCmd(acSysCmdAccessDir)

to get the path.

As for compatibility with 64 bit machines, that’ another story.
 
I think you missed what I was saying Chris. When I install my program with the ADE, it creates dirs in the program files directory, but the program won't run on 64 bit machines, because all of the files are installed in the default program files (x64) folder, instead of the normal folder name that you see in 32 bit machines. Do you know what I mean now?
 
I think I understand what you mean but I also think your program should not be hard coded to refer to its installed path. At runtime, your program should have used SysCmd(acSysCmdAccessDir) to get the installed path.

Perhaps it’s a bit late now but if you do want to change the code I would suggest not making it an absolute path but something that can be derived at runtime.
 
ChrisO has a good point.

I have Windows 7 and my directory is

C:\Program Files (x86)\Office

So this is another issue.

Best to avoid hard coding if you can and put as much as possible into Tables.
 
I think I understand what you mean but I also think your program should not be hard coded to refer to its installed path. At runtime, your program should have used SysCmd(acSysCmdAccessDir) to get the installed path.

Perhaps it’s a bit late now but if you do want to change the code I would suggest not making it an absolute path but something that can be derived at runtime.

Chris,

the path of access has nothing to do with this. the ADE packager for 07 does not allow you to change this stuff. you can choose from 5 locations where you want to install your files. Program Files is one of them. Does that make sense yet? At any rate, I really don't think there is a solution to this. For example, if I sent a deployment package to RainLover, he would not be able to run it (or rather, it would error out), because it would install all the needed files into the OTHER program files directory that is meant for the 32 bit area. He has obviously got a 64 bit machine.

BTW Rainlover, Windows I don't think has anything to do with the path.
 
Adam

I am not understanding the situation.

ChrisO may be of better help to you.

And yes I am using a 64 bit machine.
 
>>At any rate, I really don't think there is a solution to this.<<
If that assumption is correct, would it not mean the ‘end of software as we know it’?

Des does have a 64 bit machine; I was there when it arrived so you’re not telling me anything I don’t already know.

If you really want a solution then send your application to Des and we will try to load it.
But if your application, internally, can’t handle a different installation address then it is your coding that caused the problem.

Send your application to Des (Rainlover) and, if I get the chance in the coming week, I’ll go over there and we can have a look at it.
 
Seems to me that the ADE packager doesn't support the 64 bit environment.
Detecting the 64 bit environment it should change the installation path to make it work. When you install 32 bit programs a c:\program files" directory is created to support 32 bit programs. It looks like you have also installed Office 64 bit?

I had installed it (Office 2010 beta 64bit) once but it didn't seem te be downwards compatible. I couldn't run/edit Acc2003 databases. It kept asking to be converted. Removed it and using the 32 bit version now.

HTH:D
 
Adam

I am just about to take delivery of a new laptop tomorrow with Windows 7 64 bit professional setup. You have really got me concerned with compatability between 32 and 64 bit versions.

Will let you know what happens

David
 
Seems to me that the ADE packager doesn't support the 64 bit environment.
Detecting the 64 bit environment it should change the installation path to make it work. When you install 32 bit programs a c:\program files" directory is created to support 32 bit programs. It looks like you have also installed Office 64 bit?

I had installed it (Office 2010 beta 64bit) once but it didn't seem te be downwards compatible. I couldn't run/edit Acc2003 databases. It kept asking to be converted. Removed it and using the 32 bit version now.

HTH:D
Since 64 bit is native on Windows 7 64bit the C:\Program Files contains 64 bit versions of the programs you install. The C:\Program Files (x86) directory is created for the non 64bit versions. That's why ajtrumpet when installing a 32bit application the files are stored in the C:\Program Files (x86) directory.

I think that a separate installation package must be created for 32bit and 64bit systems.

Seems like a real problem to me.
 
I think that a separate installation package must be created for 32bit and 64bit systems.

I believe this is correct.. I have seen diff installers for many programs like this.. OR you are at least given the option to choose which bit version you would like to install....
 
Office 2007 is 32 bit ONLY. All 32 bit apps installed on a 64bit MS OS are loaded into Programs (x86) to keep them separate from the native 64 bit apps. I have been running Vista x64 for almost 2 years, and office 2007 a bit less than a year.

Office 2007 is designed to maximize features in Vista and 7, which don't exist in XP.

However, Office 2010 has a 64 bit version, which is about time. . . maybe then the rest of the world will design their apps to work in the 64 bit environment, like Minefield, with which I am using to browse.

sportsguy
 
Ok, I got my laptop, 64bit Windows 7 professional.

I installed my Office 2003 pro ok
Went to install Office 2007 Pro (not as an upgrade) but it failed stating it could not find a particular cab file on the CD.

I wanted to have both 2003 and 2007 installed but it won't let me. Anybody any ideas.

David
 
<<but it failed stating it could not find a particular cab file on the CD.>>

Could this simply be a case of a damaged DVD.

Suggest you copy your DVD to the Hard Drive and try again.

Sorry if this seems simplistic.
 
Don't think it's that as it is an original MS CD only used once before. There is a lot of topic on goggle about it but no resolve found. It mainly referred to 2003 not 2007.

David
 
Ok, I got my laptop, 64bit Windows 7 professional.

I installed my Office 2003 pro ok
Went to install Office 2007 Pro (not as an upgrade) but it failed stating it could not find a particular cab file on the CD.

I wanted to have both 2003 and 2007 installed but it won't let me. Anybody any ideas.

David

There are a few remarks when installing twe office versions on the same computer Here's one
and here's my own experience.
Office doesn't allow two versions to be used at the same time. Each time you start the other office version, it needs to be "installed". At least that's the message i got. After that, the version worked well untill the next switch to the other version. Again i got the "installing" message.

Yes, you can use two versions side by side but you have wait for the "installing" message.

I hope that i am making sense...

HTH:D
 
The Installing bit does not worry me as this is only a development laptop its the issue of not being able to install it alongside the 2003 version.

David
 
I did it, so it is possible.
I used MSDN subscription CD's.
Installation was uneventfull. (on Windows XP)

The use of a 64bit Office version eludes me. It is capable of addressing more internal memory and i believe it might come in handy :confused:when you have a spreadsheet/database bigger than 3GB.

When do you have such a spreadsheet/database? When your database reaches this size, it is time to switch to a bigger RDBMS such as SQL Server.

HTH:D
 

Users who are viewing this thread

Back
Top Bottom