Topics Search

Publishing database- Shut down run-time errors

Publishing database- Shut down run-time errors
Views: 12
I'm handing my database off to a client who doesn't want to split it, but also doesn't want to see any potential VBA Run-time errors. I compiled the code and digitally signed the database.

Is there a way to shut down the VBA run-time errors to a generic "error" message, or no error message at all? We don't want any users to have the option of ever pressing "debug" and getting into the
Sponsored Links:

More topics


Setting up relationships between back-end tables and front-end queries

I have an Access 2010 database that has a front end and a back end. Both are located in a shared folder on our server.

I am trying to work through the process of publishing this database to SharePoint 2010.

When I run the Web Compatibility Checker, I get the following errors:

Relationships that are not associated with a valid lookup field are incompatible with the Web.

These errors ( 3 ) are all associated with one query called Q_COMPANYDATA that is based on ODBC-linked tables on our SQL server.

Runtime Problem

I've been working on a database for 2 months with no problems. for the first time, I got an error message which read: "Execution of this application has stopped due to a run-time error. The application can't continue and will be shut down." I have never seen this message before and I have no idea what is causing it. Do I just need to reinstall the run-time engine?

correcting typographical errors

I am learning how to use Access. I have some large sets of data that I am importing from Excel and I am figuring out how to turn a flat database into a relational database (which is a very new concept to me and I am trying to get my head around it).
So I import data as a flat database and then I run the wizard to turn it into a relational database.
The thing that is bugging me is I get to a stage where Access wants to correct typographical errors. It gives me the option of making a change or selecting "Leave as is". The trouble is I don't want to correct any typographical errors. Access thinks it sees errors when there are none. BUT it flags hundreds of errors and I can't find away to "Leave as is" for all of these in one go. Instead I have to select "Leave as is" for each record in turn. This is very time consuming. Does anyone know what I am talking about and is there an easier way? I am using Access 2010 (which I think is pretty much the same as Access 2007).

Too Few Parameters

I am having a terrible time with a line of code / query.

Set appraisalRS = appraisalDB.OpenRecordset("qsAppraisalData_Output" )

simply sets a recordset. My problem is I keep getting an error when the code runs. Too few parameters. Expected 1.

I can open and run the query from the database window with no errors. I can open and run each of the queries feeding the main query with no errors.

Handle Run-Time Errors in VBA

When you are programming an application, you need to consider what happens when an error occurs. An error can occur in your application for one of two of reasons. First, some condition at the time the application is running makes otherwise valid code fail. For example, if your code attempts to open a table that the user has deleted, an error occurs. Second, your code may contain improper logic that prevents it from doing what you intended. For example, an error occurs if your code attempts to divide a value by zero. Learn how to trap run-time errors.

Autonumber field resets when publishing database to SharePoint 2010

I have a very simple table with ID (autonumber) and some other text fields. A while ago I made an append query to my ID field, starting at 9000.9001.9002.

After publishing my database to SharePoint 2010, I discovered that all IDs were reset to 1.2.3 and so on. Is this a well known problem, and can it be solved

Run time vs Full Version

I have created a database , split the database , and now I have multiple user ready to key into a form to update the table on the back end.

Sent in a request for multiple liscenses and it was denied. They told me to create the database so that they could use the database in Run Time.

Is there something that I have to do in order to allow the users to do the same work through Run Time

Error in Runtime Only

when I run my database in access 2007 I do not get any errors. when I run it in access 2007 RT I get errors and it crashes and shuts down. I don't understand how you can fix an error if their is no warning an error is occurring?

Run macros in different database

I am working with three different databases, all of which work together in certain areas, normally through linked tables. One database gets updated via csv files and the other databases get backed up primarily via this database. I am trying to automate the update process. I run the primary database update first and then I need to call macros from the other two databases to run and update the other databases. My thought was to call all of the macros from one master macro (or code) that would run daily and update the databases. In short, I am having trouble calling the macros in the secondary databases to run from the primary database.
I managed to accomplish this using the RunApp macro action but because it doesn't pause I run into a bunch of errors. Is there a better way to do this

Debugging and bypassing errors while running a query

I encountered several overflow, divide-by-zero errors while running a query. It is hard to debug this query. The errors occur only on some of the records. If I use breakpoint, it will take a very long time to step through before encountering a problematic record. Did anyone encounter similar problems and any suggestion to debug such a query?

How can I skip the errors while running the query? I have to force-close Access to stop the query from running when the errors appear