Nice and easy. For the MD5 part You could also employ Craig Boyd's vfp encrytion fll, that offers MD5 support also:

http://www.sweetpotatosoftware.com/spsblog/2009/08/09/MajorVFPEncryptionUpdate.aspx

Regards from Berlin

Could any of you pls give me a simpler way to do this. I would appreciate some simpler code that would display a form with a textbox and a dbf (not SQL).

Thanks in advance.

i want to use the mplayer in slave-mode with my vfp-application, so i have to write in the mplayer-console. do you have any informations for me.

loListener = CREATEOBJECT("RLUTF8")

TRY
REPORT FORM YourReport OBJECT loListener prev
CATCH TO loExc
MESSAGEBOX(loExc.Message)
ENDTRY

DEFINE CLASS RLUTF8 AS REPORTLISTENER

ListenerType = 1

PROCEDURE Render
LPARAMETERS nFRXRecNo ;
, nLeft, nTop, nWidth, nHeight ;
, nObjectContinuationType ;
, cContentsToBeRendered ;
, GDIPlusImage

I have some .net controls I use in VFP that were created with the Interop Forms Toolkit. Is there any way to host these directly, and if so, how would one go about it?

Thanks

Cheers

I finally found it. Under Project Properties, Linker, Input, Additional Dependencies, it was hardcoded to look for the path:

C:\programs\vs2005\SDK\v2.0\Lib\mscoree.lib

I had been modifying the VC++ Directories settings and not the Linker paths. Sheesh....

But that brings up a question that maybe you have run into? I work on two different laptops (well 3 actually). Two of them are Win7 64 and one is Win7 32. On the 64 bit machines mscoree.lib is located here:

C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib\mscoree.lib

but on the 32 bit of course it is located here:

C:\Program Files\Microsoft SDKs\Windows\v7.0A\Lib\mscoree.lib

As a test, I put the invalid directory path there along with the valid (x86) path hoping I could compile on either/or machine, but of course the invalid path errors. Is there anyway to set that so it looks only at the valid location and ignores the invalid path so I can compile on either machine so I don't have to change the setting if I compile on the 32 bit Win7 machine?

Just testing this and the error returned is:

The assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

I tried recompiling ClrHost under VS2010 (the same version my .net dll is built from) and the project cannot find mscoree.lib for some reason:

error LNK1104: cannot open file 'C:\programs\vs2005\SDK\v2.0\Lib\mscoree.lib'

I went to the project's properties and added :
C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib\x64;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib;$(LibraryPath)

to the Library Directories under Configuration Properties VC++ Directories to no avail.

Sorry for posting here - couldn't find your e-mail address.

"ApplicationHost.config lives in the <windows>\system32\inetsvr directory"

In case someone may (as I did) try to copy paste that to find it, it should instead be:

<windows>\system32\inetsrv\config

loObject = SYS(3096, lnDispHandle)

I'm writing an API that will be called by others. The API can be exposed to .NET clients as well as unmanaged C++ clients. One of my APIs actually pops a nice looking dialog that is implemented with WPF using .NET 3.5. I don't want to force the clients of my API to enable /CLR on their unmanaged apps so I will just load the CLR for them whenever they call the relevant APIs.

OK, the window I'm showing has some very custom UI elements and would be prohibitively difficult to implement in MFC or to-the-metal Win32 APIs.... This seems to be the easiest way to show WPF UI in an unmanaged client without forcing the /CLR build option on the clients.

REPORT FORM (lcReport) &lcExtraReportClauses NOCONSOLE TO FILE &lcTFile

Now I have tried the following

1 - Checked to make sure that certain settings in the "Turn Windows Features On / Off" for IIS are checked

2 - When I did this I followed you above instructions and made sure that the "IIS Metabase and IIS 6 configuration compatibility" is set.

3 - I even turned the "virtual directory" that I had created in IIS into an “application” directory.

4 – I then explored the “MIME Types” area and added a “.asp” extension. This did get rid of the above initial error “HTTP Error 404.3” but then when I tried to view the page a dialog box “File Download – Security Warning” came up saying “Do you want to open or save this file”. You can click on “open”, “save” or “cancel”. Whichever one you chose does not matter as this is not the expected result in the first place as the page should have just opened up in the browser.
5 – I also made sure that in IIS the page being requested was set as the default page to display