References: <Jmmxre$DIHA.4204@dacmail.dataaccess.com> <qZkKSUREIHA.752@dacmail.dataaccess.com> <rzM4A5XEIHA.752@dacmail.dataaccess.com> <s2Z7uXaEIHA.752@dacmail.dataaccess.com> <NPy48laEIHA.5772@dacmail.dataaccess.com> <#Y7$7DbEIHA.752@dacmail.dataaccess.com> <AeVrMSbEIHA.5772@dacmail.dataaccess.com>
In-Reply-To: <AeVrMSbEIHA.5772@dacmail.dataaccess.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <Bk8VjubEIHA.752@dacmail.dataaccess.com>
Newsgroups: Crystal-Reports
Lines: 19
Path: dacmail.dataaccess.com
Xref: dacmail.dataaccess.com crystal-reports:4707
NNTP-Posting-Host: adsl-68-255-166-222.dsl.sfldmi.sbcglobal.net 68.255.166.222

Well, just as a test, I decided to create a VB.Net based COM aware
object that I could open a crystal preview window in, using all the .Net
crystal viewers from XI R2. Surprisingly, it worked just fine. I could
pass a report in, with the path, to the object and it opens it and
connects to the SQL server.

The other surprising thing, was that it works in VDF 7 too.

So, there is an option. The only thing it would require is to write a
complete COM wrapper to the .Net components, which isn't that big of a
deal... The only drawback is the requirement of having the .Net
framework installed on the client workstations, but that is usually
installed now anyway.

If anyone wants to investigate this route further, contact me.