HeadStatusReports.jpg


Ref./Date: SR012 / 2003-11-26
Issue: Problems in Windows XP Professional when the user is logged in without administrator privileges (a "limited user").
Category: Error
Status: Open
Affected: SmartClient - All releases

Ref./Date: SR011 / 2002-05-23
Issue: Abnormal program termination after a log change.
Category: Error
Status: Closed 2002-05-31 (SmartLogger 3.3, Build 3.3.10)
Affected: SmartLogger 3.3 Build 3.3.7

Ref./Date: SR010 / 2002-02-11
Issue: When using weekly log change, the week number in the composed log name will, for some years, be offset by -1.
Category: Error
Status: Closed 2002-05-31 (SmartLogger 3.2.6, SmartLogger 3.3.10)
Affected: SmartLogger 3.2 / 3.3 Build 3.3.7

Ref./Date: SR009 / 2002-01-08
Issue: Running a frequency analysis on integer fields containing NULL values causes crash.
Category: Error
Status: Closed 2002-01-09 (SmartClient 3.3, Build 3.3.2)
Affected: SmartClient 3.0/3.1/3.2/3.3 Build 3.3.1

Ref./Date: SR008 / 2000-10-24
Issue: Potential crash of status server module when status clients (SmartStatus) are disconnected.
Category: Error
Status: Closed
Affected: SmartLogger 3.2 (Build 3.2.2), SmartTranslator 2.0 (Build 2.0.3)

Ref./Date: SR007 / 2000-05-09
Issue: Adding or removing fields from within the Print dialog after the user has rearranged the fields will cause unpredictable results.
Category: Error
Status: Closed 2000-09-24 (SmartClient 3.2)
Affected: SmartClient 3.1 (Build 3.1.0/3.1.1)

Ref./Date: SR006 / 2000-03-11
Issue: Under certain conditions the SmartClient will crash when doing an auto refresh.
Category: Error
Status: Closed
Affected: SmartClient 3.1 (Build 3.1.0)

Ref./Date: SR005 / 2000-03-06
Issue: The SmartClient crashes when trying to print a report on a PC with Windows 2000.
Category: Error
Status: Closed
Affected: SmartClient 3.1 (Build 3.1.0)

Ref./Date: SR004 / 2000-03-06
Issue: The SmartLogger program only supports serial data sources using 8 data bit.
Category: Technical note
Status: Closed
Affected: SmartLogger 3.0

Ref./Date: SR003 / 2000-02-10
Issue: Milliseconds are not stored when using MS Access 97 databases.
Category: Error
Status: Closed
Affected: SmartLogger 2.x/3.x, SmartTranslator 1.x

Ref./Date: SR002 / 1999-12-11
Issue: Milliseconds are not stored when using Oracle databases.
Category: Error
Status: Closed
Affected: SmartTranslator 1.x

Ref./Date: SR001 / 1999-12-11
Issue: Milliseconds are not shown in table grid.
Category: Request
Status: Closed
Affected: SmartClient 2.x/3.0