MS Access 2007 Run Time Error

I am working on a rather simple application in MS Access 2007.  When deploying the application as a package created with the deployment wizard included with MS Access I get the following error message from the application when running under the run time system.  Error: Run Time Error - "Execution has stopped due to a run-time error."  No further information is presented.  Any suggestions?

Thanks.
jimmurchAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

YohanFCommented:
There must be a syntax error in the program. Go to 'Database Tools' > 'Visual Basic' and from the VBA editor window go to Debug menu and select first option = 'Compile'.

It will show all the errors you will have, rectify them and try again.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ComputerAidNZCommented:
If you have complied the code that you have written (assuming you have written your own code), then it is likely a corruption on a form.  In order to rectify you need to find the errant form - difficult, then create a new DB and import all elements into the new DB, slowly and try to create the deployment package - I usually do forms first, tehn reports, then queries and so on.
0
RegnillobCommented:
You may not have a compile-time error, but a run-time error, which is an error than only shows itself when you run your application. As mentioned on the following page from Microsoft, the runtime dialog box for these errors is different and does not give much good information. You will need to run full Access on that machine or an identical environment to catch and debug the error, unless you change your code to include more error trapping.

See the "Error Handling" section of this page:
http://msdn.microsoft.com/en-us/library/cc136539%28office.12%29.aspx#Access2007BuildingRuntimeBasedSolutions_ErrorHandlinginVBACode

And further general information is at: http://msdn.microsoft.com/en-us/office/bb229700.aspx
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Boyd (HiTechCoach) Trimmell, Microsoft Access MVPCommented:
When using the Access Runtime with a accdb you must have rock solid and complete error handling for run time errors.

To find the error you will need to add error trapping code to identify the error and display a message.. I like to also log the errors

Is your database split and the front end compiled into a ACCDE?

0
Boyd (HiTechCoach) Trimmell, Microsoft Access MVPCommented:
TIP:  Rename your .accdb or .accde to a .accdr. When you open the database it will force Access into runtime mode so you can try to recreate the issue.
0
jimmurchAuthor Commented:
Tried this.  Got a clean compile under regular Access but still had general error message under run time.  Have since found my problem.
0
ComputerAidNZCommented:
So, what was the fix - so we can all learn!
0
jimmurchAuthor Commented:
The problem was my mistake.  I did not realize that the run time version generated such a limited error message.  Normally I run under the development system and do not use the run time system.

I did have error checking in my routines but in error I had deleted the last few lines in the subroutine on which I was working.  This included deleting the error checking code and the 'end sub' statement.  Apparently VBA did not find an end sub before dropping into the next subroutine.  Foolish me!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.