I read the article in following text, Do you think this will help?

I am using XBee PRO (no suffix, no S2 or series 2, etc…)
I set them with XCTU, should be 115,200 baud.

I did find this article on your site which may be the answer:

http://www.digi.com/support/forum/4787/using-the-xbee-at-115-200-baud-updated-16-march-2010

My PC is FAST, I did have a long cable on it, so will try a short one between USB and XBee Pro module.

My Embedded controller has a fast clock, 75+ MHz.
I could try adding the extra stop bit, or change baud slightly as is indicated in the article.

I am not sure what your issue is as you have not indicated it. Can you tell us what it is you are seeing and exactly which module you are working with?

I suppose I asked a related question instead of whatever I was supposed to do with previous thread. refer to “related to an answer for” above. I did not find and “add related information” button, this time I will add a comment.

I have a micro-controller that sends 87 bytes across interface (includes prefix, float data, comma separators, a suffix, a checksum and a carriage return (0x0D) to the XBee PRO (no suffix, no S2 or series 2, etc…) at 115,200 baud. I am receiving on an identical XBee PRO (no suffix, no S2 or series 2, etc…) to an i7 PC running an MSFT Visual basic (2010 version) GUI.
When I look at received data, I lose about 2 to 3 bytes per 87 byte transmission string. Checksum does not add up either.

Why are they missing?

What is the exact part number and firmware version of the modules you are using?

The part number is XBP24-DMWIT-250 revB
0013A200 403B7633

Will have to get back with firmware version, I do not know how to get that easily. I have updated some a year ago.

I would suggest looking at the NP command. The NP command reports the maximum size of the data pay load one RF packet can be.