Jozef,
According to some messages posted on the UT, SP1 should be available before year-end. However, I have no idea whether it will address the problem you describe. Here's a workaround that might allow you to deploy your app in VFP7 while producing reports with VFP6. It's certainly not pretty, but it works. The strategy is to create a COM server with VFP6 and then run the report through this COM server. I don't know how you call your reports, but I think this should be easier than redesigning all the reports.

*-- create the following in VFP6 and compile it as a COM Server (exe)
DEFINE CLASS asciiReport AS CUSTOM OLEPUBLIC

	************************************************
	PROCEDURE ReportToAscii
	************************************************	
	LPARAMETER tcReportCommand

	SET EXCLUSIVE OFF
	SET SAFETY OFF
	*-- etc.

	*-- execute REPORT command
	&tcReportCommand

	RETURN
	*-- EOF Method ReportToAscii -------------------------------------------------------------------

ENDDEFINE</font

*-- then in VFP7, instead of calling the report, use the following:
o=CREATEOBJECT("ascii.asciiReport")
o.reportToAscii("REPORT FORM  TO FILE  ASCII")

HTH
>Hi !
>I made next version of my application usimng VFP7 (previuos it was in VFP6 SP3)
>All is OK with one exception. In VFP7 REPORT FORM ASCII cuts all blank lines .
>My customers says that it is unacceptable to them, they ask me when will be next version of my application with new features that I implemented and advertise to them. I cant go back to VFP6 because VFP7 I implemented some nice new VFP7 features. I cant wait till VFP8 repair this bug and I hav no time once again design my reports. As I remember Ken Levy from Microsoft wrote on UT several weeks ago that SP should be available near end of the year. Maybe somebody could say something more precise, PLEASE ?