FIX: Coverage Profiler Does Not Accept Long Coverage File Names (221672)

The information in this article applies to:

Microsoft Visual FoxPro for Windows 6.0

This article was previously published under Q221672

SYMPTOMS

You are programmatically calling the Coverage Profiler. You pass a log file name to the Coverage Profiler as a parameter. If the log file name contains a period or periods other than one for delimiting the extension, the log file will not be opened. A file open dialog appears asking for the log file to be opened.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in Visual Studio 6.0 Service Pack 3.

For more information about Visual Studio service packs, please see the following articles in the Microsoft Knowledge Base:

194022 INFO: Visual Studio 6.0 Service Packs, What, Where, Why

194295 HOWTO: Tell That Visual Studio 6.0 Service Packs Are Installed

MORE INFORMATION

Steps to Reproduce Behavior

Run the following code from a program (.PRG) file:

CLOSE ALL
SET COVERAGE TO "A.Coverage.Log.File.With.A.Long.Name"
lnx = 1
FOR lni = 1 TO 10
   lnx = lnx + 1
NEXT
SET COVERAGE TO
DO (_COVERAGE) WITH "A.Coverage.Log.File.With.A.Long.Name"

The Coverage Profiler will start, and a file open dialog box with the caption "Please specify coverage log file" will appear.

REFERENCES

Modification Type:	Major	Last Reviewed:	10/15/2002
Keywords:	kbBug kbMiscTools kbVS600sp3fix KB221672