BR 9.2A 170720
Is there a limit for the size of a statement.csv file?

We tried to import a 505 lines statement and the import crashed with an Access Violation error message.

Split up the file into two smaller files and it imported correctly.

Hi Patricia,

The internal 'line number' field for the imported bank reconciliation file can have 5 digits, thus the theoretical maximum number of records is 100,000.

We are unaware of any problems importing bank reconciliation files of any format failing due to size. If this is something you can duplicate, then we would like a copy of the BankRec related data and the import file in order to also attempt to duplicate, and present to R&D.

Hi Patricia,

Thank you for providing the data and import files. As I have already said in my private responses to you, I was able to duplicate the access violation error with the raw import file. But if I open the file with Word 2016 and save it with no changes and deleting none of the records, the file imported successfully with all 505 lines. File size and number of records is not the problem here.

With which program did you edit the import file to remove lines and save? That could be important.

So I wonder if there is something unexpected in the file itself that import is not expecting, that gets cleaned up when saving the import file with Word (or Excel). I will pass on these findings to R&D for more investigation, but the problem might be the import file itself.

This is super weird. I copied and pasted from Notepad to Notepad. When I copied the whole file, the error persisted.
When I split the file to smaller chunks with notepad as well, it worked.

Hi Patricia,

I had someone look at the file, and the problem is that there is no CR/LF (carriage return/line feed) character at the end of the last line of the file. If you open the import file with Notepad, position the cursor at the very end of the last line, press the Enter key to add a return, and save this change, then the import will complete with no errors.

Likely while you were copying/pasting a portion of that file while testing, you were also copying the CR/LF of the last line, which is why it worked.

Thank you. I will ask the client to use another type of file or manually fix the file downloaded from the bank site.
It may also be that the file is copied when it is still opened.

A client of ours has been affected by a similar issue while trying to import detail only batch entries into the GL 9.3A 171102. Unless a blank line ended the file, the GL would simply crash without providing a useful error message.

I think there is a common problem with imports in the new releases, as import files did not previously require a trailing blank line.

Hi Warren,

When discussing this with R&D, when Patricia first reported this, the explanation I got was that in CSV formatted importing, one line at a time is read, and carriage return line feed is looked for as an indication that the current record ends there. There is no way of knowing the actual record length, and this process may not be changeable.

I have added your comments to the original report of the error. I am unaware that something has changed in newer versions as to how CSV files are read when importing.

Well, in my case the same file and the same template in GL 9.2A works without a hitch.

This has been fixed in the BankRec 92A (180209) HF.