I'm using Access 2013 32 bit on Windows 8.1 64bit. I'm attempting to test my application in the runtime mode but it causes Access to crash early in the application start phase. It doesn't appear to matter what code is running as it crashes when I try to open a file that has only tables (no macros, forms, or code modules).
I've tried running Windows Update and there doesn't appear to be any updates available. But when I look to see what updates were installed over the last day or so (I just installed Office 2013 yesterday), I can't tell that any Office updates have been installed.
Has anyone else seen this problem? Any solutions other than using something < 2013?
Related
I have here a specific application I am forced to use. This application uses Access as data storage.
This application is older and was once developed for Office 2013. Our company computers have now Office 2016 installed, with Access 2016.
After the installation of Access 2016 this application stopped running. It hangs immediately after start.
So i installed Access Runtime 2013 and application first worked fine. But as soon as I open Access 2016, there is a repair run installing something in the background and application again stopps working. After executing Repair on Access Runtime 2013, it works again until Access 2016 ist again opened.
After checking the dump of this Application I see that after running repair of Access 2013, Office15-DLLs are used. After starting Access 2016 and repair run, Office16-DLLs are linked and application stops working.
All those repair runs take minutes, so they are very annoying, as I often have to switch between both applications.
Is there any other / better way to handle it? I tried to set Runtime 2013 into the PATH of my application, no changes. Can I somehow force the application to use Runtime 2013 instead of Access 2016?
Thanks!
Please help with one issue about MS Access development.
I develop an application in MS Access 2010 Czech installation in Win10 Pro, Czech installation.
Then I use MS Access 2016 and save it in this version as a 64bit version (Czech installation) and the same windows – win10 Pro Czech.
If I run the application in Win10 Pro English installation via MS Access Runtime 2016-64bit an error rise up, see picture below.
I try out a full version of MS Access in this environment and the trouble was still running.
On my computer is working without any error.
PLEASE does anybody any experience in this problem? I am trying to solve out more than a month and it's driving me crazy.
I have got through all threads on Stack Overflow and related links. Nothing helps.
I've made an application on an MS Access 2016 with 365 subscription and deployed an .accde file. When I try to open that file on another PC with runtime installed (tried with 2016 4288-1001 64bit and 2013 64bit) I get an error saying "Database you are trying to open requires a newer version of Microsoft Access".
I know that are some issues related to runtime and 365, but some people said that using runtime 2013 solved their problem (but not mine).
Anyone have a solution for this?
The problem was that some of my table fields data was set as "Large Number".
I don't know why, but Access Runtime 2016 can't read this data type, changing the fields to "Number" made the deployed ".accde" open normally.
Source: https://support.microsoft.com/en-us/help/3208802/-database-you-are-trying-to-open-requires-a-newer-version-of-microsoft
My VS 2013 setup has been humming along fine for months now. Today I tried to update to Visual Studio 2013 Update 2 RC. Just like last time when I updated to Update 1, setup failed badly with a huge list of packages marked with the "Incorrect Hash Value" error. Unfortunately MS does not have an ISO yet for Update 2 so I can't take that route to complete the update like I did last time. Now I can't run apps on the Windows Phone emulator or on the phone (device) anymore.
I believe that the failed update caused my current deployment problems since the problem surfaced right afterwards. It could be due to some other NuGet package or Extension, but the update is the most likely cause due to the timing of events.
I did extensive reading on SO and tried all the noted solutions. None of them worked:
cleaned and rebuilt the test Windows Phone 8 project (multiple times)
restarted VS2013
rebooted
Exited VS 2013 and restarted it with the Emulator left open (for the Emulator test)
repaired the Windows Phone Emulator install
repaired the VS2013 install
Nothing works. After the IDE installs the app on to the emulator, I still an error dialog box saying:
"The application could not be launched for debugging. Ensure that the target device screen is unlocked and that the application is installed."
And in the VS2013 IDE status line I see the message: "Launching TaskHost.exe failed".
Does anyone know how to fix this? Note, I tried several WP8 projects that I know worked successfully before and none of them can deploy successfully anymore to either the Emulator or the Device.
I see this was asked a month ago, but I had this issue as well. If I left the Emulator running and tried launching it again, I would have TaskHost fail with a different error.
The following was what made it work for me.
Under the following:
Solution(Right-click) > Properties > Configuration Properties > Configuration
Ensure that your main project is set to 'Deploy.'
Have many reason to error.! So, If you doing with database such as SQLLite file or SQL compact file for your project WP, you should check it is used anywhere. Or choose Embed source copy in visual. That's my fail.And i fixed ok!
Did you try from the menus?
BUILD > Rebuild Solution
That worked for me just now.
Hi I have a application designed in access 2003 that has its front-end and back-end split. The front-end has some tables used in the UI and a lot of queries, forms, reports, and macros. This app also has a custom menu bar based on the current state of the application. I am trying to open this app using access 2010 runtime (not the full access 2010) but the application is crashing right off the bat. I get a "Execution of this application has stopped due to a run-time error. The application can't continue and will be shut down." Are there any common problems when running 2003 apps in a 2010 runtime that I could have possibily missed? Also what is the best way to troubleshoot this without using Access 2010 full version (I dont have it).
Thanks :)
Got it working. I just turned on compact and repair on close. Seemed to have fixed the problem (never was able to figure out wat it was though). The bug was only reproducible on Win7 and not WinXP