{{Quickfixn}} Problem parsing Amt fields

[Jeays, Mark]

Thanks anyway Ruaan - appreciate the time.

It turned out that we were using a modified version of QuickFix.dll that introduced a bug. Fixed now.

I'll go back to lurking...

Cheers,

Mark

________________________________________________________________

Message: 2
Date: Tue, 2 Dec 2014 07:58:52 +0200
From: Ruaan Viljoen <ruaanv at gmail.com>
To: "Mailing list for QuickFIX/n" <quickfixn at lists.quickfixn.com>
Subject: Re: {{Quickfixn}} Problem parsing Amt fields
Message-ID:
	<CAKe+C81ktBGG4izBdwdf-_zqnac_V9kAb4V-177Zxc26WdYfuQ at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Ignore my eager idiocy, that is an integer conversion of the tag number.
The culture comment was premature, I was on the wrong track.
-.-

Ruaan Viljoen


On 2 December 2014 at 07:49, Ruaan Viljoen <ruaanv at gmail.com> wrote:

> What is your decimal settings on your machine running the quickfix engine?
> It appears to be a culture issue - if your dev machine uses ',' as 
> separator, it won't parse numbers using another separator correctly. 
> If this is the case, we should consider changing conversions of 
> decimals to use InvariantCulture instead:
>
> Convert.ToInt32(msgstr.Substring(pos, tagend - 
> pos),System.Globalization.CultureInfo.InvariantCulture);
>
> Hope that helps Mark,
>
> Regards
> Ruaan
>
> Ruaan Viljoen
>