Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
FoxPro reporting from .NET
Message
 
À
13/12/2004 16:06:09
Information générale
Forum:
ASP.NET
Catégorie:
Migration
Versions des environnements
Environment:
ASP.NET
OS:
Windows 2000 SP4
Network:
Windows 2000 Server
Database:
Visual FoxPro
Divers
Thread ID:
00968898
Message ID:
00968928
Vues:
8
This message has been marked as a message which has helped to the initial question of the thread.
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
>Hello everyone,
>I have a simple question, that may have not so simple answer.
>I want to use FoxPro report from ASP.NET
>
>I know how to convert FoxPro report to PDF (printing to PostScript file and conversion using GhostScript)
>
>The problem is that for interoperability with ASP.NET, FoxPro classes should be build (to my level of knowledge) as multi-threaded inprocess COM Server. compilation results in DLL file. And when compiled in inprocess COM server, all classes automatically work in Unattended Server Mode (SYS(2335) returns 0).
>When FoxPro runs in this mode it cannot use the SET PRINTER Command.
>
>So problem is how to print from a FoxPro class that is used by .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 :)
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform