The code samples are left undefined and are inefficient. I have tried different methods and there might be a mix of solutions, but I am looking for a universal answer. What is the precision of the return values supposed to be? 32-bit signed values? That is the only way I can get it to work, but the VB6 and PB code list the return values as LONG which will return a 64-bit signed code in .NET. It bombs the code every time. I need a clarification.

---

Traders' Consortium

The return codes are int (32 bit signed).

VB6 and PB use a long differently than .NET.
.NET long is 62 bit signed.

---

Equis International, Inc.
A Thomson Reuters Company
90 S. 400 W Suite 620
SLC, UT 84101

Thanks! That is what I am finding out the hard way, but I didn't want to deviate without some assurance that I wasn't about to start chasing chickens. :fish:

We used to have a chicken chasing emoticon... where is it when you need it?!

---

Traders' Consortium

One more precision conversion question...

In structures such as MSFLSecurityInfo (just an example), there is a variable cPeriodicity. This is C++ type CHAR, an 8-bit signed value. This will convert to SBYTE in .NET, but I'm getting a lot of problems with it. It seems like BYTE will work, an 8-bit unsigned value. Will this be a problem to stick with BYTE?

---

Traders' Consortium

You should be fine with the unsigned.
It has the right number of bits and all the regular characters are positive.

---

Equis International, Inc.
A Thomson Reuters Company
90 S. 400 W Suite 620
SLC, UT 84101

Thanks!

---

Traders' Consortium