• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 560
  • Last Modified:

Access Errors: Names Conflicts, Search key errors ,and no current record Redux

Hello all!

I am getting a myriad of errors when I try to edit forms in an Access 2002 .mdb that I "inherited."  Yes, I have tried to rebuild without success, and receive the same errors during the process.

I found an earlier posting:
 (http://www.experts-exchange.com/Programming/Languages/Visual_Basic/Q_20990889.html)

that exactly describe my problems, but was resolved by the poster in a somewhat inelegant manner.  Just wondering whether two years later,  there is a cleaner solution to rebuilding a corrupt database that has gone horribly awry.  

Thanks,
Deb
0
DMV
Asked:
DMV
  • 8
  • 4
1 Solution
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
In the VBA Editor ... Tools>>References .... and be sure none are **Missing

mx
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
If any are Missing, then 'browse' to the correct file ...

mx
0
 
DMVAuthor Commented:
I wish it were so simple... no references are missing....
0
NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Me too :-)

Ok ... does it Compile?

How about Decompile ....

I would say a **DeCompile** is on order ... and also check for any **Missing References via the VBA Editor>>Tools>>References ....

Follow this procedure:

1) Compact and Repair
2) Execute the Decompile >> you database will reopen
3) Close the mdb
4) Open the mdb ... and then do a Compile (from the VBA Editor >> Menu >>Debug>>Compile<YourProjectName>)
5) Close the mdb
6) Compact and Repair one more time.


Here are sample 'links'.  Adjust your paths and file names accordingly:

Run this from Start>>Run, enter the following command line:

"C:\Program Files\Microsoft Office\Office\Msaccess.exe" /decompile C:\Access2003Clients\GoldstandtSma\App\SmaApp2K3.mdb


"C:\Program Files\Microsoft Office\Office\Msaccess.exe" /decompile C:\Access2003Clients\GoldstandtPdm\App\PdmAppl2K3.mdb

"C:\Program Files\Microsoft Office\Office\Msaccess.exe" /decompile C:\Access2003Clients\GoldstandtSma\App\SmaAppl2K3.mdb

"C:\Program Files\Microsoft Office\Office\Msaccess.exe" /decompile C:\Access2003Clients\HMC\App\AimAppl2K3.mdb

"C:\Program Files\Microsoft Office\Office\Msaccess.exe" /decompile "C:\Program Files\Microsoft Office\Office\ADIvba11LIB.mda"

For more detail on the Decompile subject ... visit the Master on the subject (and other great stuff) Michael Kaplan:

http://www.trigeminal.com/usenet/usenet004.asp?1033

mx
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Sorry ... Ignore

"I would say a **DeCompile** is on order ... and also check for any **Missing References via the VBA Editor>>Tools>>References ...."

I cut and pasted from a txt file ... but ... do try the Decompile procedure ...

mx
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
DMV ... not a lot of information to go on here ...

Any chance you can upload to:

http://www.ee-stuff.com/login.php 

Removing any sensitive data of course?

mx
0
 
DMVAuthor Commented:
Thanks mx...

First of all, I have compacted the db, decompiled and recompiled (many times) to no avail.  

Second of all,  due to the proprietary nature of the db, I am unable to upload the database.  

Lastly, I hoped that an expert who has had experience with a corrupt database could give me pointers regarding reconstructing the application. As I am getting the aforementioned errors every time I try to edit  or export a form.

Best regards,
Deb
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
ok ... I'm just pulling out all the basics ... since I have no clue what you have or have not done. btw ... I have seen decompile fix many a corrupt mdb's.  Also ... missing refs and your symptoms ... are *normally* synonymous.

So next ... how about the ole import all objects into a new mdb?  

mx
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
Also Deb ... it would probably have helped to mention from the git go that you had recently done all of the things I've mentioned :-0)

What are some of the errors (#', etc) that you are getting?  Could you post some code where the errors are occurring?  Stuff like that.

Have you tried JetComp.exe ... although, sadly ... I have never seen that fix anything :-(

mx
0
 
DMVAuthor Commented:
In short, when I try to copy, export or import (into another database) certain forms, the error “Name conflicts with existing module, project or object library” appears.

And, whenever I try to save edits to said forms, the “save” is ignored and the prompt “Do you want to save want to save changes to design of form…” appears

Best,
Deb
0
 
harfangCommented:
Hello Deb,

The question you point to is still the only final solution: import to a new database, in case of error, skip that object and continue. I had created an automated process for that (long time ago) because for some reason I managed to corrupt my VB code quite often.

First, make sure you create such a new database, one containing all tables and queries and all such forms and reports that you manage to import. Make sure the entire database is sound (compiles, can be imported in bulk to a new database, etc.)

For the broken objects, you can try several things.

1) see if the module is accessible (try to edit it)
If it is, export the module as text as backup. If not, the information is probably completely lost. In any case, try to remove the module (property Module: No) and save.

2) try to export as text.
The command is, from the immediate pane,

    SaveAsText acForm, "Your Form Name", "C:\Some\Path\And\Name.txt"

If that works, you can load it from file with the companion LoadFromFile command...

3) retrieve an earlier version from a backup
Sometimes, it's better to restart entirely, though. If it's an inherited application, try to find an old version where that form isn't yet corrupted.

Good luck!
(°v°)
0
 
DMVAuthor Commented:
Many thanks harlang with your pointer and LSM Consulting's routine (http://www.experts-exchange.com/Microsoft/Development/MS_Access/Q_21098089.html) all was recovered.

Also, thanks mx for your suggestions.

Best,
Deborah
0
 
DatabaseMX (Joe Anderson - Microsoft MVP, Access and Data Platform)Commented:
lol
0

Featured Post

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

  • 8
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now