MS Access Error

[rajeevs]

Hi
I have MS Access databases designed with Access 2010 64 Bit and now I have copied these DBs to a laptop which is running in office 32 bit. The problem I am facing is most of the time the databases are showing the error "Microsoft access has stopped working" and closes the application.
If I run the decompile command from the run command of windows the DBs work again. But again if I add any new modules, forms etc the error happens again. So it become difficult to work with multi users. Please guide me how to solve this issue.

[zmbd]

You cannot reliably open any Office-64bit document/project within an Office-32 bit installation.

In fact, Microsoft advises that users install the 32-bit version of Office, even on 64-Bit OS installations, unless you have certain very specific requirements - which most of us do not: https://support.office.com/en-us/art...e-6c6f49b8d261

> The only solution is to re-create your database in a 32-Bit installation. You, "might" be able to salvage some things; however, it is routinely suggested to start over from all of the documentation I've seen online and in tech-support.

[rajeevs]

Thank you zmbd
How about creating a blank database in 32 bit and import all the objects from the 64 bit version to this newly created DB?
Will it function properly? If not please advise then I should not spend time for doing that.

[zmbd]

see the last paragraph of my first post.
This can be done; however, the results are not always reliable...

Best bet, export your data as CSV
Import the CSV data in to the 32bit
Cut and paste any SQL from queries.
Most of the VBA will cut and paste
Rebuild the forms.
Rebuild the reports.

[rajeevs]

Hi zmbd
Sorry for the delay to reply but I was re-building the DB as per your advice. I have created a fresh DB then exported the tables and queries, but re-created the forms and reports. I know you have mentioned to cut and paste sql of the queries but I thought exporting tables and queries from the old db will be ok.Copy and paste the codes into new modules and all the events of forms and reports also copied and pasted. But still I face some inconsistency.
I am still developing that DB and always backup the DB whenever I add new things. The problem now is at certain stage when I try to open the DB it crashes and then if I open again it doesn't shows any of the vba. Can you guide me what is going wrong in this situation?

[zmbd]

If you have used any 64bit API calls in your VBA then those will have to be modified to use the 32bit. Otherwise, anything that you exported directly may be the cause of the crash in which case I would advise that you to Start over.

The only way I have seen to reliably convert 64 to 32 is the method I outlined. Do not directly import anything from the 64bit database.

[rajeevs]

Hi zmbd
I tried creating a new db from yesterday with everything new. Tables, queries, forms, reports, modules etc. I open the db today again and continued with some modifications and additions in the db. But after that I closed the db and tried to open it. The db opens but if I click any forms or modules ACCESS closes with error message. If I try to open Access from the programs it also close immediately or make a back up of the db which I closed earlier.
Any thought on this situation?
My laptop is Windows 7 (64 Bit) and Office2000 32bit.
I really dont know what is going wrong and yesterday before starting the new db I asked our IT to repair Office installation as well.
Please help me with a solution.
I sometime doubts it with the installation of office was corrupt.
Please reply

[zmbd]

Sounds as if the Office installation is corrupted.

One way to check this is to take the database to a different PC that has only ever had the 32Bit installation.

Also, you never mention the exact error messages, without that detail there is nothing anyone can do to provide any further help.

[rajeevs]

Hi zmbd

Please find attached error message screen shots. This happens when I click any forms or modules. I can open tables and queries. Reports also I can open in design mode but when i click view code, access crash with the attached error messages. Hope you can guide me about what is the actual problem. Since this DB is totally created in 32 bit I doubt it is not 32 bit issue. Please advise

[zmbd]

Unfortunately, that is a generic Windows-OS application failure.

Step One: Are you doing any API calls in the VBA module? Any 64-Bit calls will crash the application.

Step Two: let's verify some information about your install

A) Open a new, blank, database.
B) <ctrl><g>
C) In the immediate window type the following:

?application.ProductCode

Post back the string,
It should be something similar to, if not exactly like:
{90150000-000F-0000-0000-0000000FF1CE}

Step Three: let's verify that you can open and run a pure 32-Bit database:

a) Try downloading and opening the database I've recently created located in this post https://bytes.com/topic/access/answe...es#post3798522
Of course, it's a compressed file so you should extract it first. ALWAYS scan downloads for virus... although I am certain this file is clear, you never know what the blackhats will man-in-the-middle.
B) Once you have the database extracted. Close the splash form.
Open the form "Form_zz_How_I_Would_Do_This"
Select anything in the two comboboxes and then [Preveiw Effected Records]
This should update the datatable and enable the controls in the footer
Enter something in the textbox in the footer and then [Update Records]
You should see the change in the table.
C) Press <ctrl><g> to open vbe - that's all, you should be able to open the VBE and browse the code

>> If either step-two or step-three causes a system fault at any point, then it is most likely that your Office installation is corrupted.

The simple repairs may work; however, more than likely the Suite will have to be completely un-installed and re-installed. This operation is beyond the scope of this forum; however, from past experience, I highly recommend that the un-install be followed by two cold-boots before re-installing followed by at least one cold-boot after install.

[rajeevs]

Hi zmbd
Thank you for the detailed post and kind support.
The string I received after ?application.ProductCode is "{90140000-0011-0000-0000-0000000FF1CE}"
But yesterday after posting my questions I have done a decompile from the Run cmd for the specific DB and it started working again.
But today again after working with the same DB adding some forms, queries and report it still shows the error.
I have downloaded the DB.
I will go through your steps and advise you the progress

[rajeevs]

Hi zmbd
I tried your DB and followed the instructions. It is working fine.
Any thought on my post #11? before posting that I have asked our IT to re-install Office and done all those after the re-installation.
Do you still doubt this is a corrupt office installation / 32 bit 64 bit issues?

Regards

[zmbd]

Ok, so, the pure database opens and you can look at the underlying code. That's the good part; however, looking at the product code.
"{90140000-0011-0000-0000-0000000FF1CE}"
From Microsoft support:
Release version: Original install - no service packs
Release type = Volume license
Major version = 14
Minor version = 0000
Product ID = Microsoft Office Professional Plus 2010
Language = This appears to be relying on the system language
Install = 32bit
Production release

>> Looks like your IT department needs to obtain and install service pack 2 for Office 2010. This may very well resolve your problems.
Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition

or via> Microsoft>Office Updates - IT

My other question, are you making any API calls, for example, to pull the user name from the OS?

[rajeevs]

Hi zmbd
Thank you for the guidance. I will check with IT and get the update.
Second question: Yes I try to get usernames on form open and use login forms which check and authenticate the domain password.
But it was ok when I used these functions in 64Bit. Please advice.
Service pack issue I will reply you tomorrow because my working time in office is finished.

[zmbd]

Let's see what the SP2 install brings about... there could still be something amiss with one of the office components.

Should have suggested this back in my prior post, take the current DB to a different PC with 32bit install and open there...