# Unable to read the Ini File Iterator

**URL:** https://www.finalbuilder.com/forums/t/unable-to-read-the-ini-file-iterator/1252
**Category:** Discussion
**Created:** [July 7, 2009, 2:11am UTC](https://www.finalbuilder.com/forums/t/unable-to-read-the-ini-file-iterator/1252 "2009-07-07T02:11:36Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [July 7, 2009, 2:11am UTC](https://www.finalbuilder.com/forums/t/unable-to-read-the-ini-file-iterator/1252/1 "2009-07-07T02:11:36Z")

</div>

Hi ,

i am using a very simple Ini File Iterator, i am able to read the half of the .ini file very well but after&nbsp;some 900 iterations, &nbsp;its unable to read the next section.

i doubt that their should be a size limitation on the .Ini file or some problem with the Ini&nbsp; File Iterator ? please clarify me.

for more informatin, i am attaching a sample finalbuilder project.

regards

Rasheed

&nbsp;

[001\_Test.zip](https://www.finalbuilder.com/forums/uploads/default/original/2X/2/21ae4c87c6b10bdb0d976f7dbb32fb7dc6cc667f.zip) (8.204 KB)

---

<div class="post-metadata">

### Author: ![paulsamways](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/p/e8c25b/32.png) [@paulsamways](https://www.finalbuilder.com/forums/u/paulsamways)
#### Post date: [July 8, 2009, 1:12am UTC](https://www.finalbuilder.com/forums/t/unable-to-read-the-ini-file-iterator/1252/2 "2009-07-08T01:12:45Z")

</div>

Hi Rasheed,   
  
 I wasn’t able to reproduce the problem with the latest build of FinalBuilder 4, could you confirm that you’re running the latest version of FinalBuilder 4 (4.2.0.317).   
  
 If you aren’t, you can download the build from [https://www.finalbuilder.com/download.aspx](https://www.finalbuilder.com/download.aspx) after being logged in.   
  
 Regards,   
 Paul.

---

<div class="post-metadata">

### Author: ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [July 8, 2009, 7:57am UTC](https://www.finalbuilder.com/forums/t/unable-to-read-the-ini-file-iterator/1252/3 "2009-07-08T07:57:21Z")

</div>

Hi Paul,   
Strange ....still i am able to reproduce the problem with latest version of Finalbuilder-4 (4.2.0.317)&nbsp;and Finalbuilder-6 (6.3.0.1506)&nbsp;, could you directly run my above sample&nbsp;project&nbsp;on your machine and kindly update me.

&nbsp;there are around 7623 sections but my finalbuilder project iterate around 1821 times and comes out from the loop, which should not be.&nbsp;  
  
kindly help me out in this issue.   
  
regards   
Rasheed.

---

<div class="post-metadata">

### Author: ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [November 12, 2009, 3:10am UTC](https://www.finalbuilder.com/forums/t/unable-to-read-the-ini-file-iterator/1252/4 "2009-11-12T03:10:00Z")

</div>

I am seeing a the same problem except that I am only able to read about 431 entries out of 9000 before it stops. It reports success, but it clearly is not iterating through the entire section.   
  
 To eliminate an issue with file format I deleted 25 lines around the area that it would stop at, but it always stops at line 431 and says it has iterated through the entire section.   
  
 I am using FB 6.3.0.1472.   
  
 Any help or advice would be greatly appreciated.   
  
 Thanks,   
 Josh

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [November 12, 2009, 8:25am UTC](https://www.finalbuilder.com/forums/t/unable-to-read-the-ini-file-iterator/1252/5 "2009-11-12T08:25:49Z")

</div>

This was fixed in the most recent release version available from our website.