When trying to do "Compact and Repair Database", it shows the error message: No Current Record : Microsoft, Access, 2000, No Current Record

May 17, 2008 05:12am pdt

1. capricorn1 1,301,290
2. DatabaseMX 890,113
3. LSMConsu... 482,407
4. boag2000 335,153
5. harfang 313,826
6. peter57r 272,376
7. TextReport 229,085
8. GRayL 209,614
9. ee_rlee 170,073
10. cactus_data 154,536
11. jimhorn 151,903
12. matthews... 147,637
13. JezWalters 137,435
14. jefftwilley 126,171
15. puppydog... 102,935

1. capricorn1 8,958,328
2. nico5038 5,685,831
3. rockiroads 5,398,237
4. peter57r 3,716,871
5. LPurvis 3,361,835
6. shanesue... 3,288,317
7. LSMConsu... 3,217,997
8. harfang 2,930,659
9. stevbe 2,838,604
10. DatabaseMX 2,773,449
11. jimhorn 2,571,495
12. GRayL 2,369,458
13. flavo 2,104,083
14. mbizup 1,976,668
15. jadedata 1,963,977

05.09.2008 at 02:38PM PDT, ID: 23390882

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

9.7

When trying to do "Compact and Repair Database", it shows the error message: No Current Record

Zones: Microsoft Access Database, General Office Suite Software

Tags: Microsoft, Access, 2000, No Current Record

We have an Access 2000 database that's usually around 140 MB. We routinely run the Compact and Repair Database function to keep the database size down to that level and to maintain good end-user responsiveness. Suddenly when I try to do the Compact and Repair Database function, it bombs out about halfway through and displays a "No Current Record" error (and no corresponding number or anything). The database seems to be running fine otherwise.

I've tried copying the database to another PC and running Compact and Repair but I get the same error (even on a box with Access 2003). I've also tried decomiling/recompiling the database, which is about the only relevant solution I found on EE, but that didn't work either.

Any idea as to why we can no longer compact the database?

Thanks,
Jeff

Start your free trial to view this solution

Question Stats

Zone: Microsoft

Question Asked By: mschmidt14

Solution Provided By: harfang

Participating Experts: 2

Solution Grade: A

Translate:

Loading Advertisement...

Microsoft

Internet Protocols
Applications

Development
OS

Hardware
Windows Security

Apple

Operating Systems
Hardware

Programming
Networking

Software

Internet

Search Engines
File Sharing
WebTrends / Stats
Spy / Ad Blockers

Web Browsers
New Net Users
Web Development
Chat / IM

Anti Spam
Web Servers
Anti-Virus
Email Clients

Gamers

Tips
Online / MMORPG
Puzzle
Emulators

Action / Adventure
Role Playing
Consoles
Game Programming

Strategy
Sports
Misc
Computer Games

Digital Living

Hardware
New Net Users
New Users

Software
Digital Music
Gaming World

Home Security
Apple
Networking Hardware

Virus & Spyware

Vulnerabilities
IDS
Encryption
Anti-Virus

Operating Systems Security
Software Firewalls
WebApplications
Cell Phones

Operating Systems
Internet
Hardware Firewalls

Hardware

Handhelds / PDAs
Displays / Monitors
Components
Networking Hardware

Peripherals
Laptops/Notebooks
Storage
Servers

Desktops
New Users
Misc
Apple

Software

System Utilities
Industry Specific
Network Management
Photos / Graphics
Page Layout
VMWare
Misc
Web Development

OS
CYGWIN
Voice Recognition
Message Queue
Quality Assurance
Security
Firewalls
MultiMedia Applications

Development
Database
Office / Productivity
Business Management
OS/2 Apps
Server Software
Internet / Email

ITPro

OS
Storage
Encryption
Operating Systems Security
Apple Hardware
Laptops & Notebooks
Servers
Networking Hardware
Peripherals

Devices
Displays / Monitors
WebTrends / Stats
Search Engines
Firewalls
WebApplications
IDS
Vulnerabilities
Email Clients

File Sharing
Spy / Ad Blockers
Web Browsers
Web Servers
Networking
Anti-Virus
Chat / IM
Anti Spam

Developer

Web Servers
Web Browsers
Game Programming
Dev Tools
Industry Specific
Office / Productivity

Database
CYGWIN
Web Development
Search Engines
File Sharing
WebTrends / Stats

Programming
Content Management
Application Servers
Protocols

Storage

Removable Backup Media
Storage Technology
Servers

Grid
Remote Access
Backup / Restore

Misc
Hard Drives

Miscellaneous
Security
Development
Linux
VMWare

MainFrame OS
Unix
Apple
OS / 2
AS / 400

BeOS
Microsoft
VMS / OpenVMS

Database

Oracle
Miscellaneous
MySQL
Software
Sybase
Contact Management
PostgreSQL
Data Manipulation
Clarion
InterSystems Cache

Siebel
MUMPS
OLAP
SQLBase
SAS
GIS & GPS
4GL
Berkeley DB
DB2
Informix

Interbase / Firebird
FoxPro
Reporting
LDAP
Filemaker Pro
MS SQL Server
dBase
MS Access

Security

Misc
Web Browsers
Software Firewalls
Operating Systems Security
File Sharing

Spy / Ad Blockers
Vulnerabilities
WebApplications
IDS
Anti-Virus

Encryption
Anti Spam
Email Clients
VPN
Chat / IM

Programming

Editors IDEs
Installation
Handhelds / PDAs
Multimedia Programming
System / Kernel

Algorithms
Game
Signal Processing
Project Management
Open Source

Database
Misc
Languages
Processor Platforms
Theory

Web Development

Scripting
Blogs
Web Servers
Software
Search Engines
Web Graphics
Images

Internet Marketing
Images and Photos
Components
Document Imaging
Web Languages/Standards
Illustration
WebApplications

Fonts
WebTrends / Stats
Authoring
Digital Camera Software
Miscellaneous

Networking

Protocols
Apple Networking
Network Management
Message Queue
Application Servers
Content Management
File Servers
Email Servers
Misc
Java Editors & IDEs

Wireless
Networking Hardware
Backup / Restore
System Utilities
ISPs & Hosting
Web Servers
Storage Technology
Removable Backup Media
Servers
Broadband

Grid
OS / 2
Novell Netware
Unix Networking
Windows Networking
Security
Telecommunications
Operating Systems
Linux Networking

Other

Community Advisor
Lounge
Community Support
New Net Users

Philosophy / Religion
Math / Science
Miscellaneous
URLs

Expert Lounge
Politics
Puzzles / Riddles

Community Support

Suggestions
New to EE
New Topics
Community Advisor

CleanUp
Announcements
General

Feedback
Input
EE Bugs

05.09.2008 at 02:44PM PDT, ID: 21536571

Rank: Genius

DatabaseMX:

" I've also tried decomiling/recompiling the database,"

Using what procedure ?

mx

05.09.2008 at 02:52PM PDT, ID: 21536604

mschmidt14:

I don't have that solution handy any longer, but I remember running some command at the command prompt with the /decompile switch, then I went into the DB and recompiled within VB.

05.09.2008 at 03:01PM PDT, ID: 21536641

Rank: Genius

harfang:

This looks like data / index corruption. It might be a little tricky to recover. First, keep all present backups (hopefully from before this started), as you might wish to explore them in order to reconstruct corrupted data.

Before we start: you don't have any code running, do you? If the process starts, it's obviously not the case, but I wanted to make sure. If you are not sure, open the database while holding down the Shift key.

The easiest test is to import your tables into a new database. Normally, the import process will regenerate all indexes. If that fails, you should at least have an idea about which table is affected. Skip over that one and continue.

To retrieve data from the corrupted table (if you have one), try to copy-paste in chunks. You can also browse it for any unusual data. Sometimes, it "bombs out" simply when attempting to read a given record. Hopefully, you will be able to reinsert the missing data from a backup.

Other possible steps are: remove all relationships, attempt to remove all indexes, attempt to delete the corrupted record (if you found it), delete all objects but the tables...

Problems that "compact and repair" cannot fix are usually nasty, so be prepared for some long hours. I sincerely hope that simply importing into a new database will work!

(°v°)

05.09.2008 at 03:01PM PDT, ID: 21536643

Rank: Genius

DatabaseMX:

Here you go:

A **DeCompile** may help here ...

But first, if you have not already:
Check for any **Missing References via the VBA Editor>>Tools>>References ....

Then, follow this procedure:

0) **Backup your MDB**
1) Compact and Repair the MDB, as follows:
Hold down the Shift key and open the MDB, then from the menu >>Tools>>Database Utilities>>Compact and Repair ...
2) Execute the Decompile (See example syntax below) >> after which, your database will reopen.
3) Close the mdb
4) Open the mdb and do a Compact and Repair (#1 above).
5) Open the mdb:
a) Right click over a 'blank' area of the database window (container) and select Visual Basic Editor. A new window will open with the title 'Microsoft Visual Basic' ... followed by then name of your MDB.
b) From the VBA Editor Menu at the top of the window:
>>Debug>>Compile
Note ... after the word Compile ...you will see the name of your 'Project' - just an fyi.

6) Close the mdb
7) Compact and Repair one more time.

*** Executing the DeCompile **EXAMPLE**:
Here is an **example** of the command line syntax (be SURE to adjust your path and file name accordingly) for executing the decompile:

Run this from Start>>Run, enter the following command line - **all on one line** - it may appear like two lines here in the post:
Also, the double quotes are required.

"C:\Program Files\Microsoft Office\Office\Msaccess.exe" /decompile "C:\Access2003Clients\YourMdbNameHERE.mdb"

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

05.09.2008 at 03:15PM PDT, ID: 21536706

mschmidt14:

DataBaseMX-
Actually, your response is exactly what I read and followed in another EE issue, so it must be a copy-and-paste response. I can't even perform your step #1 because I'm getting the "No Current Record" error when trying to compact and repair - that's the whole reason for my question.

Harfang-
I just tried opening the DB with the shift key held down but I still get the error upon performing compaction. I'll try importing the tables into a new DB and report back.

Thanks,
Jeff

05.09.2008 at 03:18PM PDT, ID: 21536722

Rank: Genius

DatabaseMX:

Sorry ... I meant to preface that post with 'skip the initial Compact & Repair part'

mx

05.09.2008 at 03:37PM PDT, ID: 21536814

mschmidt14:

DatabaseMX: Oh, OK. I tried the whole process and I still get the error.

Harfang: I created a new database and successfully imported all tables without errors. I did a compaction at that point and it went fine. I assume I should import everything else now (queries, forms, reports, etc.) and see what happens?

05.09.2008 at 03:38PM PDT, ID: 21536822

Rank: Genius

DatabaseMX:

"I assume I should import everything else now (queries, forms, reports, etc.) and see what happens?"

Definitely.

mx

05.09.2008 at 04:01PM PDT, ID: 21536918

Rank: Genius

harfang:

That is GOOD news, believe me!

Depending on how you imported the tables, you might have to recreate your relationships. Post-mortem diagnostic: it was one of the indexes, probably a primary key index. When compacting, the engine follows the primary key order (with an effect similar to defragmenting a hard drive). An entry existed in the index, but the corresponding record didn't, hence: "no current record". The mystery is why "repair" didn't recover from that gracefully. Perhaps because it would potentially delete data without your knowledge?

(°v°)

Accepted Solution

05.14.2008 at 10:15AM PDT, ID: 21566455

mschmidt14:

I haven't yet got around to importing anything besides the tables into the new database, but I tried compacting today on a whim and it worked fine. So for whatever reason, the orignal database is compacting fine again and the issue disappeared.

Thanks for the assistance, EE experts!

Jeff

05.14.2008 at 02:17PM PDT, ID: 21568819

Rank: Genius

harfang:

Well, indexes don't corrupt easily. Now that it's refreshed, you might never encounter the problem again. In fact, I know of at least two Access specialists who keep a collection of corrupted files for testing purposes!

(°v°)

20080236-EE-VQP-29 / EE_QW_2_20070628