>VFP reports will run from a VFP COM .exe(with the REPORT FORM in it and PDF stuff) and you can call that from a VFP mtdll which will interop with .NET. Interop with .NET will require a .NET proxy dll to be generated over the VFP mtdll using TLBIMP or VS.NET

>>My ideas for workarounds:
>>1. Printing from another COM class build as out-process COM server (EXE file)
>>2. Refactor the report as crystal reports one.
>>
>>I would like if someone has a better idea, to share it :)

OK, thanks for the info but your suggestion is not different from option 1 (I should have been more specific, I guess)
Also the other guys has suggested either option 1 or 2... So I guess that there is no 3rd approach (at least that is known by the public)

Kind Regards