Apparent Microsoft Bug - 08/21/2007 - Improperly Captured Data

Two separate incidents of failure of Cap2002 to properly update the mm.db1
file have a common cause and interim solution. A Type 1 Processor puts out
a short string of 4 numbers separated by 3 commas every 10 seconds. A Type 2 
Processor puts out a long string of 8 numbers separated by 7 commas every 10 
seconds. The Cap2002 program determines the processor type by the string length
where 1,0,0,0,0,0,0,10000 (shortest possible from Type 2) is longer than 18 characters 
and   16,255,64000,64000 (longest possible frome Type 1) is not.

If Cap2002 is receiving the shorter string from a Type 1 processor and handling it as
a Type 2, the result is a malformed entry at the end of the mm.db1 file and 
this condition prevents Dis2002 from rendering a report. This can happen on an
intermittent and unpredictable basis. Cap2002 v1.15 made improvements to the 
code to detect which type is in use but it appears that:

Certain instructions in VB 6.0 are ignored by certain computers under certain conditions.

The interim fix is to download and use Cap2002v15csamp.exe which has all Type 2 logic removed
when working with Type 1 processors only.  

Code being ignored:

'16,255,99999,99999  = 18 max mM 1
'1,0,0,0,0,0,0,10000 = 19 min mM 2
If sw2 < 1 Then 'v15 do once
 If Len(c1$) > 18 Then sw1 = 1
 If Len(c1$) < 4 Then sw1 = 4
 sw2 = 1
End If
If sw1 = 0 Then Label3 = "mMI"
If sw1 = 1 Then Label3 = "mMII"