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.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Boyd (HiTechCoach) Trimmell, Microsoft Access MVPDesigner and DeveloperCommented:
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

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.
Boyd (HiTechCoach) Trimmell, Microsoft Access MVPDesigner and DeveloperCommented:
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.
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

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.
Boyd (HiTechCoach) Trimmell, Microsoft Access MVPDesigner and DeveloperCommented:
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.
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..

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
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.
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.