BUG: SSCommand Control Generates Application Error

MORE INFORMATION

Steps to Reproduce Bug

1. Start Visual Basic 4.0, or if it is already running, click New Project on the File menu.
2. Click Custom Controls on the Tools menu. Click the Sheridan 3D Controls check box in the Custom Controls dialog box. Click OK to close the dialog box.
3. Add a SSCommand control to the Form1 form.
4. Add the following code to the Form1 code window:

      Private Sub SSCommand1_Click()
   
         'Set the SSCommand button's Picture property to the PictureBox
         'control's default property as below:
         SSCommand1.Picture = Form2.Picture1
   
         'The workaround is to explicitly specify the PictureBox control's
         'Picture property. Use the following code instead:
         'SSCommand1.Picture = Form2.Picture1.Picture
   
      End Sub
   
   					

5. Add a second form to your project by clicking Form in the Insert menu.
6. Add a PictureBox control to Form2 form.
7. Set the PictureBox control's Picture property to any bitmap or icon file stored on your computer as follows:
   1. In the PictureBox control's Properties Window, click the button with an ellipsis (...) to display the Load Picture dialog box.
   2. Double-click any listed bitmap (.bmp) or icon (.ico) file.
8. Press the F5 key or click Start on the Run menu to start the Visual Basic program. Click the Command1 button. The caption changes to bitmap graphic you selected. Click the End button in the toolbar to stop the project. An application error occurs with one of the following messages displayed and Visual Basic ends:

   Windows 2000

      32-bit: No Errors, appreas to work okay.

      16-bit: VB caused a General Protection Fault in module VB.Exe at
              0023:39FF.

   Windows NT 3.51:

      32-bit: An application error has occurred and an application error
              log is being generated. VB32.Exe Exception: access violation
              (oxc0000005), Address: 0x0046e951.

      16-bit: VB caused a General Protection Fault in module VB.Exe at
              0023:39FF.

   Windows 95:

      32-bit: VB32 caused an invalid page fault in module VB32.Exe at
              0137:0046e951.
      16-bit: VB caused a general protection fault in module VB.Exe at
              0023:000039ff.

   Windows 98:

      32-bit: VB32.EXE caused an invalid page fault in module VB32.Exe at
              015f:0046e951.
      Or:
              VB32.EXE caused an invalid page fault in module KERNEL32.DLL
              at 015f:bff7b9e3.

      16-bit: Same as Windows 95.

   Windows (and Windows for Workgroups) 3.11:

      VB caused a General Protection Fault in module VB.Exe at 0023:39FF.