Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...The enviroment is simple, natural and efficient. The members are competent, educated and professionals..."

Geography

Where in the world do Tek-Tips members come from?
kwomack (Programmer)
19 Apr 12 10:38
I have an Access ADP project that was created in Access 2003. Recently we upgraded to Access 2010. The APD connects to an SQL 2000 database. The ADP works fine until I try to make changes. After making changes and reopening the project, the project crashes shortly after I open it. It happens even if I hold down the shift key to prevent the AutoExec code from loading or a form from loading. I can open the project and do nothing but wait and about 15-30 seconds later it closes with an error "Access has stopped working". I have tried compact and repair. I tried creating a new ADP, connecting it to the same database and importing the forms, modules, and reports from the old ADP but Access crashes while copying the forms. It does not matter which form I try to copy. I am running Windows 7 64-bit with Office 2010 32-bit. Any ideas will be appreciated.
kwomack (Programmer)
19 Apr 12 11:06
After searching for 2 weeks to find the solution, I post here and 10 minutes later find a solution. To fix the issue, run msaccess in /decompile mode and then open the Visual Basic editor and compile the code from the debug menu. I found several procedures that were left over from prior updates that references objects that no longer existed in the application. Commenting out these procedures allowed the database project to compile.

I guess this means Microsoft is forcing us to be better developers and not leave code behind just because we are to lazy to clean it up.  

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close