ID: Q161695
The information in this article applies to:
When attempting to use the import file command to add an .frm file (a form) to a Visual Basic for Applications project, you may receive a message similar to the following:
Errors during load. Refer to <path>\<filename>.log for details.
After you click OK to acknowledge the error message, the form opens.
However, most controls are missing and the form may not behave as expected.
When you export an .frm file, the Visual Basic Editor stores binary information vital to the operation of the form and its child controls in an .frx file. When you import an .frm file, the corresponding .frx file must be available within the same folder. If the .frx file has been modified, damaged, or is missing you may receive the error.
When you export an .frm file the Visual Basic Editor automatically creates the .frx file in the same directory. So, when moving the form, make sure you keep the .frx and .frm files together.
The .frx files should never be modified manually. Modifying the .frx files results in unpredictable behavior when accessing the associated form.
For more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: Q163435
TITLE : VBA: Programming Resources for Visual Basic for
Applications
Additional query words: 97 8.00 kbmacro ppt8 vba vbe macppt mac_ppt ppt98
98 powerpt
Keywords : kbcode kberrmsg kbmacro kbprg kbdta kbdtacode kbpptvba
Version : WINDOWS:97; MACINTOSH:98
Platform : MACINTOSH WINDOWS
Hardware : MAC x86
Issue type : kbprb
Last Reviewed: December 15, 1998