FIX: GetPrivateProfileInt() May Not Read Correct Value
Article ID: 111602
Article Last Modified on 10/16/2002
APPLIES TO
- Microsoft Windows Software Development Kit 3.1
This article was previously published under Q111602
SYMPTOMS
If GetPrivateProfileInt() is used to read a number that has preceding white
space, the value returned may be incorrect. For example, if the .ini file
entry is as follows, GetPrivateProfileInt() may return 0 (zero):
MyValue= 5
CAUSE
This problem is caused by the white space in front of the number.
RESOLUTION
Ensure that any numbers written to an .ini file do not contain white space.
STATUS
Microsoft has confirmed this to be a bug in Windows version 3.1. This bug
was corrected in Windows 95.
Additional query words: whitespace
Keywords: kbbug kbfix kboswin95fix kb16bitonly kbsyssettings KB111602