What this error message actually tells you

When Microsoft Access shows "Handle Chr 10 30 Lines" or a similar message during a query, it means Access encountered a line break character (Chr 10) in your data and is telling you how many instances it found. This is not a fatal error — it is Access reporting what it discovered in your records. The message appears because Access is processing text that contains actual line breaks, which can happen when data was pasted from another program, entered with manual line breaks, or imported from a system that stores multi-line notes.

The number after "Chr" (in this case, 10) refers to the ASCII code for a line break character. The number after that (30) tells you how many lines or instances of this character exist in the field or result set. Understanding what triggered this message helps you decide whether to clean the data, adjust your query, or leave it as is.

Key Takeaways

  • Chr 10 is the line break character in text — the same thing that happens when you press Enter inside a cell or text box.
  • The number 30 means Access found 30 instances of that line break in the data your query is processing.
  • This message usually appears when you import data from Excel, email, or web forms that contain multi-line text fields.
  • You can remove these characters with the Replace function in a query, or leave them if the line breaks are intentional.
  • The message does not mean your query failed — it means Access is reporting what it found in your data.

Where line breaks come from in your data

Line breaks end up in Access fields most often when you import data from Excel spreadsheets that have wrapped text, or when you paste content from email, Word documents, or web forms. A notes field that someone typed into over multiple lines will contain Chr 10 characters at each point where they pressed Enter. If you export data from another database system, that system may use line breaks to separate information within a single field.

You might also see this message if you are working with data that came from a form where users entered comments in a multi-line text box. Access stores those line breaks as Chr 10 characters, and when you run a query that processes that field, Access can report how many it found. The message itself is not a warning that something is wrong — it is straightforward Access telling you what is in your data.

How to find and remove line breaks in a query

If you want to remove the line breaks, you can use the Replace function in a calculated field within your query. In the query design view, create a new field and use a formula like this: CleanedField: Replace([YourFieldName], Chr(10), " "). This tells Access to take the original field, find every instance of Chr 10, and replace it with a space. You can also replace it with nothing (empty quotes) if you want the text to run together without spaces.

Another option is to use Replace with Chr(13) and Chr(10) together, since some systems use both characters for a line break: Replace(Replace([YourFieldName], Chr(13), ""), Chr(10), ""). This removes both the carriage return (Chr 13) and the line feed (Chr 10). Test the formula on a copy of your data first to make sure the result looks the way you want it.

When to leave line breaks in your data

If the line breaks are intentional — for example, if a notes field is supposed to show information on separate lines for readability — you do not need to remove them. Line breaks do not break queries or cause data loss. They only affect how the text displays when you view it in a form, report, or exported file. If your query is working correctly and the data looks right when you view it, the Chr 10 message is just informational.

Line breaks can actually be useful in reports. When you place a field with line breaks into an Access report, the text will wrap naturally at those break points, making multi-line notes easier to read. If you are exporting data to Excel or another program, line breaks may display differently depending on how that program handles them, but they will not corrupt your data or cause the export to fail.

Understanding ASCII codes in Access

Chr 10 is one of several special characters that Access can work with using the Chr function. Chr 10 is the line feed (the character that moves the cursor down one line). Chr 13 is the carriage return (a holdover from typewriter days that moves the cursor to the beginning of the line). Different systems use different combinations — Windows typically uses both together, while older Mac systems used only Chr 13, and Unix systems use only Chr 10.

When you see a message mentioning Chr and a number, that number is the ASCII code for a specific character. Chr 9 is a tab, Chr 32 is a space, and Chr 34 is a quotation mark. Knowing the number helps you write formulas to find and replace exactly what you need. Access documentation lists all the ASCII codes if you need to work with other special characters.

Why Access reports this during queries

Access shows this message because it is designed to alert you when it encounters unexpected characters in your data. Older versions of Access were stricter about what characters could appear in certain fields, and the message is a remnant of that design. Modern versions of Access handle line breaks without problems, but the message still appears to keep you informed about what is in your data.

The message is most common when you are importing data or running a query on a field that was not created in Access originally. If you are building a database from scratch and entering data directly into Access forms, you are less likely to see this message because Access forms handle line breaks cleanly. The message becomes more frequent as you work with data from external sources.

Frequently Asked Questions

Does Chr 10 mean my query has an error?

No. The message is informational — it tells you what Access found in your data, not that something went wrong. Your query is working correctly. The line breaks are part of your data, and Access is straightforward reporting their presence.

Can I prevent line breaks from being imported in the first place?

You can use the Replace function during import if you are using a linked table or import specification. When you set up the import, you can create a transformation that removes Chr 10 as the data comes in. For one-time imports, it is often faster to clean the data after import using a query with the Replace function.

What happens if I ignore this message and leave the line breaks in?

Nothing bad happens. Your data remains intact, your query continues to work, and the line breaks stay in the field. They will display as line breaks when you view the field in a form or report. Only remove them if the line breaks are not supposed to be there or if they are causing display problems in a specific report or export.

How do I know if the line breaks are supposed to be there?

Look at the original data source. If the field in Excel or the source system shows text on multiple lines, the line breaks are intentional. If the text should be on one line but appears broken up, the line breaks were added accidentally during import or data entry, and you should remove them.

Can line breaks cause problems when I export data to Excel?

Line breaks usually export fine to Excel and will display as wrapped text in the cell. Some older versions of Excel or specific export settings might handle them differently, but in general, line breaks do not cause export failures. Test an export with a small sample of data if you are concerned about how a specific program will handle them.