Access 2007 App test Win 10. 'Execution of this application has stopped due to a run-time error'.

[Edward_]

I'm testing an Access 2007 .MDE application and matching tables.mdb in a couple new Windows 10 PCs.
Just to maybe to get things a bit more current than Win 7.



I have tested this same app in Win 8.1 with good results, operates as expected, but in Win 10, the mde opens, but quits after I select the location of the data tables.
Displaying: 'Execution of this application has stopped due to a run-time error'.

This crash occurs at the point where my app has failed to find the data tables, and after I have browsed to the data file location and submitted.
I realize I'm asking a vague question, but was hoping there may have been a common issue with Win 10 someone else may have experienced.

What might be a good first step in identifying the cause of this error? Like a non-existent OCX or DLL.

Any advice appreciated.

[Edward_]

Resolved temporarily.

After manually registering MSCOMCT2.OCX in C:\Windows\System32 folder all operated properly.
(64 Bit Win 10, but app running from 'Program files (x86)'.

After power cycling the PC, the same run-time error occurs...

[Micron]

What might be a good first step in identifying the cause of this error

I'd start by obtaining the original db and making a copy on the W10 pc. Open it there and see if there are any missing references in the code project. If none found, I'd then step through the code to see if I could figure out which line was causing it - assuming any code runs at all. You might find that variables need to be declared PtrSafe if you're running old code in a 64 environment.

[Edward_]

Thanks Mircon.

I do have the original MDB, I'll test it on the Win 10 with runtime ASAP.

[Edward_]

The MDB opens as desired. No error.

But none of the forms will allow text entry, with an error chime sound.

Maybe to do with the opening warning that states the DB is Read Only.
Apparently the data tables are read only. But I have set the Tables MDB file permissions to full access Read/Write.

The top left corner Office Button is sort of flashing constantly also.

[Micron]

Are the db parts (FE and BE) in a Trusted Location where you put the copies?

[Edward_]

The FE is in a folder I created in the 'Program Files(x86)' folder. The BE is in C:\Program data\appData folder now.

It IS working now from the MDE FE.

I set all of the Permissions for full Read/Write for all groups, for the folder containing the FE(that is in the Program Files(x86) folder.

[Micron]

I don't think that really answers the question. Are those locations designated as Trusted Locations in Access?

[Edward_]

Yes, forgive me,
Using the MS Office button in 2007 Runtime doesn't list Access Options, to get to the Trust Center, Trust Center Settings, Trusted Locations.
Or my app is preventing the Options from displaying. The Runtime doesn't let me do a Hold-Shift startup to see all menus either.

[Micron]

You seem to be jumping ahead. All testing should be in your accdb or mdb copy; doing nothing with any run time version until you're satisfied the original version works in W10

[Edward_]

Thanks again Mircon,
I now have the trusted locations setup for FE and BE, created in the MDB.

I'm now hoping to eliminate the unrelenting Security Notice 'A potential security concern has been identified' dialog displaying on startup (in the non origin Win 10 test PC). (I have created a digital certificate for the original MDB, before creating the FE MDE)

My BE is local for testing purposes, not on a network drive.

[Micron]

You remembered to re-link your fe to the new be location? Otherwise, it's still using the old location.
The security notice sounds like a level of trust option for running code needs to be tweaked. Wondering if the first suggestion in this reply has anything to do with it.

[Edward_]

You remembered to re-link your fe to the new be location? Otherwise, it's still using the old location.

I removed the old BE.mdbs completely.
My app has a feature that checks for the presence of the BE on starup, if not found on startup, it prompts the user to browse for and select the BE.mdb, then writes the path to the registry, then starts.

[Micron]

Still sounds like a trust issue
https://community.spiceworks.com/top...een-identified (one of many such links)
which leads to
https://getadmx.com/?Category=Office...nsOnTheNetwork

unless maybe permissions, since

I set all of the Permissions for full Read/Write

isn't enough for a normal db. Create and delete are needed for normal db's, in order to create and remove the locked database file (laccdb or ldb in older versions). I say normal because that's what I'm used to - have 0 experience with run time, sorry.

[Edward_]

Do you think Trusted Network Locations would pertain to my error with FE & BE in same PC?
And, would you think that the trusted locations from the master MDB would be echoed to the MDE?
I would think so.

I added 'D:\' trusted location in my MDB, then ran it under Access 2007 runtime in the test PC, with my MDB file in D:\ .

The Security Notice 'A potential security concern has been identified' dialog is still displayed.