Microsoft KB Archive/246307: Difference between revisions
m (Text replacement - "<" to "<") |
m (Text replacement - """ to """) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 78: | Line 78: | ||
<li>Open Visual FoxPro 6.0 and create a new project.</li> | <li>Open Visual FoxPro 6.0 and create a new project.</li> | ||
<li><p>Add a new program to the project with one line of code:</p> | <li><p>Add a new program to the project with one line of code:</p> | ||
<pre class="codesample">MESSAGEBOX( | <pre class="codesample">MESSAGEBOX("HELLO!") | ||
</pre></li> | </pre></li> | ||
<li>With the project selected, press the CTRL+J key combination to bring up the '''Project Information''' window.</li> | <li>With the project selected, press the CTRL+J key combination to bring up the '''Project Information''' window.</li> | ||
| Line 86: | Line 86: | ||
<div class="errormessage"> | <div class="errormessage"> | ||
APPLICATION ERROR. The instruction at <memory address | APPLICATION ERROR. The instruction at <memory address> referenced memory at <memory address>. The memory could not be "read". | ||
</div> | </div> | ||
<div class="errormessage"> | <div class="errormessage"> | ||
An application error has occurred and an application error log is being generated. <exe name | An application error has occurred and an application error log is being generated. <exe name><br /> | ||
Exception: access violation:<memory address | Exception: access violation:<memory address>, Address:<memory address> | ||
</div> | </div> | ||
Latest revision as of 13:50, 21 July 2020
Article ID: 246307
Article Last Modified on 10/16/2002
APPLIES TO
- Microsoft Visual FoxPro 5.0 Standard Edition, when used with:
- Microsoft Windows NT 4.0
- Microsoft Visual FoxPro 5.0a, when used with:
- Microsoft Windows NT 4.0
- Microsoft Visual FoxPro 6.0 Professional Edition, when used with:
- Microsoft Windows NT 4.0
This article was previously published under Q246307
SYMPTOMS
When building a Microsoft Visual FoxPro (VFP) executable, it is common practice to attach a custom icon to it. Usually, the custom icon contains two or more resources. This allows the icon to be displayed in various Windows views (small icons, large icons, details, and so forth). If the custom icon contains a 16x16 resource with more than 256 colors, the resulting .exe file does not run on Microsoft Windows NT 4. When the .exe file is started, it immediately exits with a memory error.
RESOLUTION
Build the 16x16 resource in the custom icon with 256 colors or fewer.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
Steps to Reproduce Behavior
- Using Microangelo (manufactured by Impact Software: http://www.impactsoft.com/muangelo/muangelo.html) or some other icon editor, create an icon. Include a 32x32 resource with 256 colors, and a 16x16 resource with more than 256 colors.
- Open Visual FoxPro 6.0 and create a new project.
Add a new program to the project with one line of code:
MESSAGEBOX("HELLO!")- With the project selected, press the CTRL+J key combination to bring up the Project Information window.
- Use the Attach Icon checkbox to attach the icon created in step 1 to the project.
- Build the project into an executable.
- Run the .exe file on a computer running Microsoft Windows NT 4, and note that one of the following error messages appears:
(c) Microsoft Corporation 1999, All Rights Reserved. Contributions by Trevor Hancock, Microsoft Corporation.
REFERENCES
For additional information about creating icons for use with Visual FoxPro executables, click the article numbers below to view the articles in the Microsoft Knowledge Base:
136044 How to Make ImagEdit Create 16X16 Icons
149589 How to Ensure that Custom Icons Show Up in Windows 95 Explorer
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Keywords: kbbug kbcodesnippet kbappsetup kbpending KB246307
