# Ini File Iterator confused by lines with same item name

**URL:** https://www.finalbuilder.com/forums/t/ini-file-iterator-confused-by-lines-with-same-item-name/3251
**Category:** Bugs
**Created:** [July 28, 2010, 5:31am UTC](https://www.finalbuilder.com/forums/t/ini-file-iterator-confused-by-lines-with-same-item-name/3251 "2010-07-28T05:31:44Z")
**Posts on this page:** 2
**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 28, 2010, 5:31am UTC](https://www.finalbuilder.com/forums/t/ini-file-iterator-confused-by-lines-with-same-item-name/3251/1 "2010-07-28T05:31:44Z")

</div>

I’m using FinalBuilder 6.3.0.2026.   
  
 I have an Ini File Iterator which is set to Iterate over a Section’s Values, putting the Name into Scan\_ItemName, and the Value in to Scan\_ItemValue.   
  
 When I do this with a file that has two lines with the same Name, but different values, I see the first data twice and the second data not at all.   
  
 eg. the lines:   
  
 SomethingElse=another   
 SomethingElse=something completely different   
  
 Will load the Name “SomethingElse” twice, but with the Value “another”. It doesn’t even matter if there are items with other names between the two lines (in the one section).   
  
 Is this expected behaviour?   
  
 Included is a tiny sample (script and data).[TestIni.zip](https://www.finalbuilder.com/forums/uploads/default/original/2X/b/b25399b7c1f68d56aa4e545a7aaf69c6d4caaa4d.zip) (1.813 KB)

---

<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 28, 2010, 5:47am UTC](https://www.finalbuilder.com/forums/t/ini-file-iterator-confused-by-lines-with-same-item-name/3251/2 "2010-07-28T05:47:36Z")

</div>

Ah, my fault.   
  
 It seems this is quite legitimate for handling .ini files. I wasn’t aware of that.   
  
 It still strikes me as odd, and it would be neat if each successive value could be presented, rather than lost (from what I understand, such behaviour wouldn’t be incorrect - the situation is explicitly undefined).
