Dave, after I thought I'd fixed the problem, I continued to
encounter other errors that seemed related to the same
problem, that Excel 97 thinks the modules are worksheets.

I have numerous cases in which I loop through all the
worksheets in the workbook, such as turning protection off
or on in order to make some changes to protected cells. The
sheet counter moves past the last sheet, and goes into the
modules, giving a type mismatch error.

e.g.:

Set wb = ActiveWorkbook
For Each sht In wb.Sheets
setProtection sht, False
Next sht

Public Sub setProtection(wks As Worksheet, bStatus As Boolean)
With wks
If bStatus Then
.EnableSelection = xlUnlockedCells
.Protect DrawingObjects:=True, Contents:=True,
Scenarios:=True
Else
.Unprotect
End If
End With
End Sub

-Kate

Dave Peterson wrote:
> I've never seen this problem.
>
> But back with xl95, macros were saved in macro sheets (before the VBE was
> invented).
>
> Any chance you're saving as xl95?
>
> You should be able to save as a normal workbook--the file format for xl97, xl2k,
> xl2002, xl2003 are all the same.
>
> ===
> When bad things happen to good modules, maybe it's time to run Rob Bovey's code
> cleaner:
>
> You can find it here:
> http://www.appspro.com/
>
> Kate wrote:
>
>>I'm attempting to re-program a workbook which I originally
>>designed in Excel 2003, to run in Excel 97 also.
>>
>>I've discovered a few annoying items, such as
>>worksheet-changes not being triggered when data validation
>>drop boxes are used. However, this one has me bamboozled:
>>
>>Modules randomly appear as tabs in the worksheet. When this
>>happens, the whole thing locks up and must be crashed
>>out-of. This only happens with stand-alone modules, not
>>with code that is associated with each sheet.
>>
>>Does anyone have any idea how to resolve this issue? I need
>>these modules to be available to all the sheets at all times.
>>
>>Thanks, in advance,
>>Kate
>
>