Access 2010 Runtime on a 32 bit Office on a 64 bit Operating System.
I am having a problem with one client who is trying to run a small access database on his computer using Runtime, this database works perfectly in the 32 bit environment but he has tried this on the Runtime for 32 bit and for 64 bit and nothing seems to be working. The latest message I have is "Execution of this Application has stopped due to a Runtime Error"
Any help would be greatly appreciated. We were told to download "service pack 2 for Office 2010" but we cant find the link and I dont know if this is the answer - please experts help me.
Any help would be greatly appreciated. We were told to download "service pack 2 for Office 2010" but we cant find the link and I dont know if this is the answer - please experts help me.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Going to try MZ Tools now, thank you, will let you know how it goes
ASKER
OK, I have tried MZ Tools and yes it is amazing, however it is also a bit above my level of expertise and I will ask a couple of my colleagues to look at it as well.
I need advice please. We need to buy another computer, we produce a std database sold to all different platforms and we need to be able to test and run on all of them. In future we think we will not do runtime but that doesnt matter at the moment.
If we buy a 64 bit machine with 64 bit software (windows and office) - will a database created on this run on Access 2007 on windows 7 or earlier? -- I think the answer is NO but need to double check
I need advice please. We need to buy another computer, we produce a std database sold to all different platforms and we need to be able to test and run on all of them. In future we think we will not do runtime but that doesnt matter at the moment.
If we buy a 64 bit machine with 64 bit software (windows and office) - will a database created on this run on Access 2007 on windows 7 or earlier? -- I think the answer is NO but need to double check
Definitely NO for Office2010. You must use 32-bit Office , whether you run 32bit or 64bit windows. But that's only one issue.
In addition , the chances of you building an app in Access2010 that runs OK in Access 2007 are minimal. Backwards compatibility is almost non-existant from A2010 to A2007.
If you are distributing to customers who are using A2007 then you MUST produce your app using A2007.
In addition , the chances of you building an app in Access2010 that runs OK in Access 2007 are minimal. Backwards compatibility is almost non-existant from A2010 to A2007.
If you are distributing to customers who are using A2007 then you MUST produce your app using A2007.
ASKER
Hi Peter, than you for your answer. At present our largest selling database runs perfectly in 2010 and 2007 on 32 bit, however people are buying 64 bit and the first time we had a problem with this was trying to use a runtime. If we do not do runtime anylonger (I detest it anyway) are you suggesting we dont need to buy a 64 bit (because of backward compatibility). Please I am not asking for total commitment, just your expertise and experience.
Thank you as always for your help.
Thank you as always for your help.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Now that would be hilarious, if I knew how this had happened I would tell you, but this database has been going for nearly 10 years, has grown and grown, been changed from version to version, developer to developer, sections added to (gov regulations) and taken away (yes I know the developers nightmare) but it is stable and runs perfectly in both versions (apart from 64 bit runtime) and used by medium and small business alike. Although we dont recommend more than 20 users, on average it is a 5 -10 user installation. Shoudl they need to go larger we recommend they use a database with SQL. We do not have mixed users, i.e. they must all be on the same version of Access. We always split the databases etc.
We do have some API's but not a lot. I really appreciate your help on the 32 bit and 64 bit, it has been invaluable, thank you.
We do have some API's but not a lot. I really appreciate your help on the 32 bit and 64 bit, it has been invaluable, thank you.
OK - so is it still an mdb file then?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have done the following and it has helped, but dont know if it will work with all machines
- Open your application, and go to Database tools and Visual Basic, which will open the VB Code.
- Click “Find”, and search for the word “Declare”
- When it finds a statement something like “Declare Function…….”
- Add the word PtrSafe to the statement so it reads “Declare PtrSafe Function”
- Open your application, and go to Database tools and Visual Basic, which will open the VB Code.
- Click “Find”, and search for the word “Declare”
- When it finds a statement something like “Declare Function…….”
- Add the word PtrSafe to the statement so it reads “Declare PtrSafe Function”
But I don't think I can help you with the problem.
The only issue I can think of that could cause a problem is the use of API calls - many declarations have to be modified for use in a 64-bit environment.