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
Related
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 run MS Access 2010 on my home PC and I've been building a database for work.
Most workstations at work don't run Access to build databases, but they do allow us to run MDE files for applications already built.
I saved my database as a 2002-2003 database and then published it as an MDE file. All worked really well. I tested the MDE file on my PC at home and the automatic re-linking to the back end db worked and the database popped up. Awesome.
The problem came when I tried to run it on the workstation. It came up with an unrecognized format and suggest I change the version on the database.
So, back to the drawing board. I did some research and from all indications from other forums and sites, you cant build MDE files for 2002-2003 databases using Access 2007 or 2010, even though the option is clearly there.
Suggestions were to load Access 2003 to the PC an build the database using this. OK, did that, imported all of the items from the 2003 database created in Access 2010 to a blank db created in 2003 and I get nothing but errors. Incidentally the database was originally build from and access 2003 database at work! Unfortunately, I no longer have access to that particular workstation.
So that's the dilemma. The question / discussion im after is how to resolve this and get the database, preferably from my office 2010 suite into a standalone system of some type working from a Windows XP workstation at work.
I need to find a way to be able to build these tools at home and use them at work. BTW, upgrading the workstations at work is not an option. believe me the organisation is too large to even consider a change like that, WAY too much bureaucracy..
As mentioned in one of the comments to your question, if you are targeting an older version of Access then you should be doing your development in that version, not a newer one. Even though Access 2010 allows us to create an .mde file that is in the Access 2003 file format, it may actually create an .mde file that Access 2003 cannot understand due to the contents of the file.
The situation is analogous to the problem of making certain modifications to an Access 2007 database in Access 2010+ that render it unusable by Access 2007. Even though the file format is still "Access 2007 or later", Access 2010 may create database objects within that file that Access 2007 cannot comprehend. Depending on the actual objects involved, Access 2007 may simply ignore what it doesn't understand, but unfortunately in some cases Access 2007 will just give up and say "Unrecognized database format".
I have an MS-Access 2013 application (.accdb) with only couple of tables and forms in it. I am trying to deploy it on another machine that has only MS-Access 2013 runtime installed. Problem is my access application opens up on that machine with a security warning but doesn't show any object in it. Not even access ribbon. What am I missing or doing wrong?
Solution suggested by #HansUp and then explained by #PowerUser in comments, worked like a charm.
I inherited an access 2003 ADP file which uses sql 2000 as it's data source. This is my first access maintenance project and not thinking about the issues involved simply opened it in access 2007 on my dev machine. It of course worked and I proceeded to do the work requested.
I have completed the work and presented the file to the client, which he opens in access 2003 and proceeds to receive several errors, all related to variables not being declared. It is at this point I realize that none of the code files have Option Explicit set. I look at the project in access 2007 again - no errors. The behaviour is as if access 2007 is respecting the Lack of Option Explicit and working as expected, but access 2003 "thinks" Option Explicit is set, even though it never appears in any code files.
I realize I could just re-do the work using only access 2003, but that would be more time-consuming than I'd like.
Weird problem - I can't see how Access 2003 would check for explicit varible declarations without any Option Explicit. Something else must be going on.
Can you reproduce the behaviour on your machine using Access 2003?
How about you actually declare your variables? You should have Option Explicit set regardless.
UPDATE:
Since the goal is to try and get the Access 2003 mdb (saved from 2007) working. I would try one more thing.
Using Access 2003 open the mdb with the /decompile switch
Make a backup of your mdb
Open your mdb (hold the SHIFT key down to stop any code from running) via a short cut: msaccess.exe database.mdb /decompile
Open a module and compile your app
Save and close Access
Open again (SHIFT again) without decompile
Compact and repair database
close Access
This isn't going to help you much, but I learned very quickly when one of my clients switched over to Office 2007 that I should NEVER work on a 2003 db in 2007 and then try to run it in 2003. Developing in 2007 then converting to 2003 doesn't work either. Developing in 2003 and then running the 2003 db (without conversion) in 2007 works pretty well. Most of the time.
A possible answer for the second part of your question:
1. Convert your 2007 db to 2003 format.
2. Open a new empty db in 2003
3. Import all objects from the converted 2003 db. Recompile, and try it on your client's machine.
I had this problem too. I am 2 years into developing an Access 2003 front end that connects to an SQL backend. I started to use Access 2007 thinking all I had to do was save in 2003 format and all would be well.
Not so. All my users still using 2003 reported problems.
The problem was easy to solve in the end. I didn't actually use any 2007 features and so all that was changed was the library references. I had 2 missing references to the Word and Excel 12.0 libraries, which were automatically included just by opening the database in 2007.
Took those references out and I was able to 'fix' my database without having to revert back to an earlier version.
Anyone knows if it is possible to install Access 2003 standalone without the rest of the Office 2003? I seem not to locate my installation disks to test this out, but thought someone might have an answer...
I believe so, when you install Office and choose custom install, you can deselect everything except Access.
You can do a custom install and then deselect everything.
You will basically get all the MS Office run-time and shared components with only the Access application available to run.
Note: I don't use the access run-time any more, but do use it regularly for the Excel and/or Word applications.