Rick wrote his own solution for passing non standard types back to VFP in this article:
http://www.west-wind.com/presentations/VfpDotNetInterop/vfpDotNetInterop.htm
Sounds like a similar problem. His solution is very neat but simple!
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Stephen Russell Sent: 04 May 2016 16:54 To: ProFox Email List profox@leafe.com Subject: Re: SQL Server Reporting Services Web Service
That will only make the .dll you need to instantiate. the problem is what will VFP do with the object you receive form it that is outside of the realm of objects that VFP can deal with? Could you receive a List<T> ? I don't think so but then I don't try to push VFP anymore either.
On Wed, May 4, 2016 at 10:39 AM, Paul Newton Paul.Newton@pegasus.co.uk wrote:
Any hints as to how I create a COM-callable .NET DLL ? Do I just create a new solution/project based on "Class Library" ?
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Alan Bourke Sent: 04 May 2016 14:45 To: profoxtech@leafe.com Subject: Re: SQL Server Reporting Services Web Service
At this point then I would be thinking about
(a) Writing a COM-callable .NET DLL which provides a simpler interface for VFP into SSRS or (b) Writing a Powershell script to do it, then running that through the Windows Scripting Host from VFP.
The latter probably involves pain around permissions though
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]