Opening an Access Form (2010)

We are getting the "execution of this application has stopped due to a run-time error". when opening a form from the main application window.
The program is being run using Access 2010 Run-time version.
The machine is run from a Windows XP with sevice pack 3 system and all the updates.
The database resides on a 2008 R2 server in the same subnet as the desktop client.
The database application was created on a different subnet and when you run it from a machine on the subnet it was created, it works great. Both are identical machines (desktops) except for the subnet. When you run it from a system on the other subnet (where the user resides) we get the error mentioned above.
We have another 2010 access database application being used that works great from either subnet.
woodsbwAsked:
Who is Participating?
 
woodsbwAuthor Commented:
We appreciate your insight. We ended up moving the application to SQL and it works great. Keep the points, Your feedback did provide us with some valuable insight..
0
 
Boyd (HiTechCoach) Trimmell, Microsoft Access MVPCommented:
Note: Since 1993 I have never had any issue with any version of Access related to the subnet.

Sounds like a database issue not a network issue. The only issue I have seen with a network is folder permissions,. The user must have read/write permissions on the folder with the database.


<<The database resides on a 2008 R2 server ..>>
Does this mean that only the back end is on the server?

If not, then that is the first issue that need resolved.  See:  Splitting your Access database into application and data

0
 
woodsbwAuthor Commented:
I understand what you are saying about splitting the database and application. I  am still confused why this was not a problem with another access database currently being used in another department. I will move ahead with splitting the database and application. Hopefully this will resolve the issue. I will post either way.
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:
Splitting is only a part of the issue.

My suspicion is that there is an issue with that individual form.form

Since the database is not split I would assume that you are not using a accde as the front end.

Any database used in the access runtime that is not complied into a accde must have very rock solid and complete  error handling.  I cover this in my article in the link I provided above.
0
 
woodsbwAuthor Commented:
Ok. Splitting the database did not resolve the issue. Making the ACCDE did not complete due to the following:
This error is usually associated with compiling a large database into an MDE file.  Because of the method used to compile the database, a considerable number of TableID references are created for each table.  The Access database engine can only create a maximum of 2048 open TableIDs at one time.  Exporting a database as an MDE potentially can exceed this limit if the database has a large number of objects (table, macro, form, report, etc).
There is no accurate method to estimate the number of TableIDs the Access database engine uses during the process of compiling a database as an MDE.  However, each VBA module and each form uses one TableID, as a result, if the database has 500 forms, and each form's HasModule property is set to Yes, as many as 1,000 TableIDs are used.
0
 
Boyd (HiTechCoach) Trimmell, Microsoft Access MVPCommented:
I would create a new blank front end database.  Import all teh object from the old front end into the new front end. Set the VBA references. Compile the VBA code. If it complies then try to make the ACCDE.

Note: Rebuilding a database like this help with corruption and other issue.  I do this on most fron tend databases  after making lots of design changes.
0
 
woodsbwAuthor Commented:
While the Expert did provide us with some valuable insight abut our problem, we felt it was better for us to move to SQL as the solution.
0
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.

All Courses

From novice to tech pro — start learning today.