Data error obstructing scans

   SPH seems to be creating problems for my scans.
Most of my scans were not working this weekend, due to a data error. Check, reason for rejection table.

"Data error: Item has already been added.Key in dictionary: 'SPH' Key being added: 'SPH'

A work around is to delete the stock code SPH from all lists that you wish to scan. 

Author	Message / View First Unread Post Share Topic Printable Version Delicious Digg Facebook Furl Google Boomarks Google Buzz MySpace Newsvine reddit StumbleUpon Translate Twitter Windows Live Yahoo Bookmarks Topic Search Topic Options Post Reply Create New Topic
peter1 Members Profile Send Private Message Find Members Posts Add to Buddy List Regular Joined: 27 Aug 2008 Location: Sydney Posts: 55	Post Options Post Reply Quote peter1 Report Post Quote Reply Topic: Data error obstructing scans Posted: 18 Jun 2011 at 5:05pm
	SPH seems to be creating problems for my scans. Most of my scans were not working this weekend, due to a data error. Check, reason for rejection table. "Data error: Item has already been added.Key in dictionary: 'SPH' Key being added: 'SPH' A work around is to delete the stock code SPH from all lists that you wish to scan.

peter b Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 10 Mar 2006 Location: Australia Posts: 2	Post Options Post Reply Quote peter b Report Post Quote Reply Posted: 23 Jun 2011 at 11:14pm
	I seem to be encountering the same bug. Copying each list and saving after removing SPH will get to be a bit of a drag. Any ideas for how to fix this properly, anyone? I don't run scans every day so I'm not sure when it started, but I do remember downloading the latest version of Microsoft.Net Framework for another application, the day before.

administrator Members Profile Send Private Message Find Members Posts Visit Members Homepage Add to Buddy List BullCharts Staff Joined: 09 Sep 2004 Location: Australia Posts: 2	Post Options Post Reply Quote administrator Report Post Quote Reply Posted: 24 Jun 2011 at 10:14am
	This problem occurs with BullCharts V. 3.6.7 or below. You may have to upgrade your BullCharts to V.3.8.6 to fix the problem. for more details regarding How to upgrade to V.3.8.6, please contact us via: Email: info@bullysystems.com Telephone: 02 9495 8400 Sorry for the inconvenience NOTE: To check your BullCharts version, click "Help" > "About BullCharts"