Solved: How do I fix Microsoft Access “No current record” Run-time error 3021

This blog article explains how to fix MS Access error 3021 – No current record. MS Access error 3021 – No current record occurs when MS Access fails to read the current record in the queries, which can be caused by various factors, such as corruption, deletion, incorrect path, or insufficient permissions.

The article provides four solutions to fix this error, such as granting permissions, using BOF or EOF properties, checking the SysData folder’s path, or using the Compact and Repair tool. The article also answers some FAQs related to this error, such as how to prevent it, how to repair the database file if the Compact and Repair tool fails, and how to refresh the linked tables or queries.

Problem

MS Access is a popular database management system that allows users to create and manipulate data in various ways. However, sometimes users may encounter errors that prevent them from performing their tasks smoothly. One of such errors is the MS Access error 3021 – No current record, which indicates that MS Access fails to read the current record in the queries.

This error usually arises when using the Recordset objects (DAO) in the VBA code for modifying the records in the Access database. In this article, we will explain the causes and solutions of this error, and provide some tips to avoid it in the future.

Causes of MS Access Error 3021 – No Current Record

There are several possible reasons why MS Access error 3021 – No current record may occur. Some of the common ones are:

• The Access database records are corrupted or damaged due to various factors, such as power failure, virus attack, improper shutdown, etc.
• The current record is deleted or moved by another user or process while the Recordset object is trying to access it.
• The mapped drive or network path to the shared SysData folder, where the database file is stored, is incorrect or inaccessible.
• The user does not have sufficient permissions to edit the database file that is saved in the shared SysData folder.
• The path of the shared SysData folder is incorrect or changed in the FRx32.cfg file, which stores the configuration settings for FRx Designer.

Solutions to Fix MS Access Error 3021 – No Current Record

Depending on the cause of the error, there are different methods that can be used to fix MS Access error 3021 – No current record. Here are some of the effective solutions that you can try:

Solution 1: Grant Permissions to SysData Folder

If the error is caused by inadequate permissions for editing the database file that is saved in the shared SysData folder, you need to grant the required permissions to the folder. To do this, follow these steps:

Step 1: Open the folder and right-click on it, then click on Properties.

Step 2: Under the Attribute, make sure that the Read-Only checkbox is not selected. If it is selected, clear it and click OK.

Step 3: After this, click on the Security tab and click Edit.

Step 4: Verify that all the users have Write, Read, Modify, and Read & Execute permissions for that folder. If the users do not have these permissions, add them and click OK.

Solution 2: Use BOF or EOF Properties

Another method that you can try to fix MS Access error 3021 – No current record is to use the BOF (Beginning of File) or EOF (End of File) properties for checking the records. These properties return True if the current record position is before the first record or after the last record, respectively. By using these properties, you can avoid the error when there are no records in the Recordset object. For example, you can use the following code to check if the Recordset object is empty before accessing the fields:

If Not (rs.BOF And rs.EOF) Then
    'Access the fields here
Else
    MsgBox "No records found"
End If

Solution 3: Check the SysData Folder’s Path

If the error is caused by an incorrect path of the shared SysData folder in the FRx32.cfg file, you need to edit the file to show the correct SysData location using UNC (Universal Naming Convention) mapping. To do this, follow these steps:

Step 1: Locate the target directory for the FRx32.exe, which launches FRx Designer. The default location is C:\Program Files (x86)\FRx Software\FRx 6.7.

Step 2: Edit the FRx32.cfg file in this directory using Notepad, to show the correct SysData location using UNC mapping. For example:

[SysData]
Directory=\\Servername\Sharename\SysData\

Step 3: Save the changes to the FRx32.cfg file and open FRx Designer.

Note: Do not edit the FRx32.cfg file before opening FRx Designer, as this can cause loss of data in the shared SysData folder.

Solution 4: Use Compact and Repair Tool

If the error is caused by corruption or damage in the Access database records, you need to repair the database file using the Compact and Repair tool in MS Access. This tool can help you fix minor errors and reduce the file size by removing the unused space. To use this tool, follow these steps:

Step 1: Open MS Access and click on the Database Tools tab.

Step 2: Click on the Compact & Repair Database button.

Step 3: Select the database file that you want to repair and click OK.

Step 4: Wait for the process to complete and then open the database file again.

Note: Before using the Compact & Repair tool, make sure that you have a backup copy of the database file, as the tool may delete some data during the repair process.

FAQs Related to MS Access Error 3021 – No Current Record

Here are some of the frequently asked questions related to MS Access error 3021 – No current record:

Question: How can I prevent MS Access error 3021 – No current record from occurring in the future?

Answer: To prevent MS Access error 3021 – No current record from occurring in the future, you can follow some best practices, such as:

• Keep your database file in a secure and accessible location, and use UNC mapping instead of mapped drives or network paths.
• Regularly backup your database file and use the Compact and Repair tool to maintain its health and performance.
• Use proper error handling and validation techniques in your VBA code to avoid unexpected situations and errors.
• Close the Recordset object and release its resources after using it.

Question: How can I fix MS Access error 3021 – No current record if the Compact and Repair tool fails to repair the database file?

Aswer: If the Compact and Repair tool fails to repair the database file, it means that the database file is severely corrupted or damaged. In that case, you need to use a professional Access Database Repair Software that can recover the data from the corrupted database file and restore it to a new file. One of the recommended software for this purpose is Stellar Repair for Access, which can repair corrupt MDB and ACCDB database files and recover deleted database tables, queries, indexes, and records easily.

Question: How can I fix MS Access error 3021 – No current record if the error occurs in a linked table or query?

Answer: If the error occurs in a linked table or query, you need to check the source of the link and make sure that it is valid and accessible. You can use the Linked Table Manager tool in MS Access to refresh the links and update the data. To use this tool, follow these steps:

Step 1: Open MS Access and click on the External Data tab.

Step 2: Click on the Linked Table Manager button.

Step 3: Select the linked tables or queries that you want to refresh and click OK.

Step 4: If prompted, enter the new location or password for the source of the link and click OK.

Summary

MS Access error 3021 – No current record is a common error that occurs when trying to modify the records in the database using the Recordset object or VBA code. This error can be caused by various factors, such as corruption, deletion, incorrect path, or insufficient permissions. To fix this error, you can try the solutions mentioned in this article, such as granting permissions, using BOF or EOF properties, checking the SysData folder’s path, or using the Compact and Repair tool. If these solutions do not work, you can use a professional Access Database Repair Software to recover the data from the corrupted database file.

Disclaimer: This article is for informational purposes only and does not constitute professional advice. The author is not liable for any damages or losses that may arise from the use of the information or software mentioned in this article. The user is responsible for verifying the accuracy and validity of the information and software before using them.