D
dgmoore
We recently migrated from WinNT to XP Pro. I have a large Access app
(Access2K) that makes heavy use of acSysCmdSetStatus to allow users to
monitor progress. This worked perfectly under WinNT, but under XP the
status line updates only occasionally, and seemingly at random. Record
counters quit in the middle, the acSysCmdClearStatus statement gets
ignored, etc. This behavior is inconsistent and changes from one
session to another - sometimes the SetStatus works correctly during a
given procedure and sometimes it doesn't.
Does anybody have any suggestions or experience with this?
Thanks
Dave
(Access2K) that makes heavy use of acSysCmdSetStatus to allow users to
monitor progress. This worked perfectly under WinNT, but under XP the
status line updates only occasionally, and seemingly at random. Record
counters quit in the middle, the acSysCmdClearStatus statement gets
ignored, etc. This behavior is inconsistent and changes from one
session to another - sometimes the SetStatus works correctly during a
given procedure and sometimes it doesn't.
Does anybody have any suggestions or experience with this?
Thanks
Dave