FIX: RW2002 Error From Long Resource Identifier

 Last reviewed: September 16, 1997
Article ID: Q99389
1.00 1.50 | 1.00 
WINDOWS   | WINDOWS NT
kbtool kbfixlist kbbuglist kbfasttip

The information in this article applies to:

  • The App Studio included with: 

        - Microsoft Visual C++ for Windows, versions 1.0 and 1.5
    - Microsoft Visual C++, 32-bit Edition, version 1.0

SYMPTOMS

An attempt to build resources in App Studio fails and App Studio generates the following message: 

   error RW2002: File not found

CAUSE

If a bitmap, cursor, or icon has an identifier longer than 23 characters, App Studio incorrectly generates the resource file. As the identifier grows beyond 23 characters, it eliminates spaces between the identifier and the resource statement. Eventually, the identifier displaces the resource statement to the right. If the identifier is long enough, it eliminates spaces between the resource statement and the memory option.

STATUS

Microsoft has confirmed this to be a problem in App Studio version 1.0 for Windows and App Studio version 1.1 (32-bit). This problem was corrected in Visual C++ 32-bit Edition version 2.0.

More Information

App Studio generates a line like the following for the IDB_THISISAVERYLONGIDENTIFIER identifier: 

   IDB_THISISAVERYLONGIDENTIFIERBITMAPDISCARDABLE "filename.bmp"
It should generate the following: 

   IDB_THISISAVERYLONGIDENTIFIER BITMAP DISCARDABLE "filename.bmp"

Additional reference words: 1.00 1.10 1.50
KBCategory: kbtool kbfixlist kbbuglist kbfasttip
KBSubcategory: AppStudioIss
Keywords : AppStudioIss kbbuglist kbfasttip kbfixlist kbtool
Version : 1.00 1.50 | 1.00
Platform : NT WINDOWS
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.