Well, I have a kludge you can use without the control.
Put a button on your form, then on the On Click event,
Capture the value in the text field, and then create an html file and drop it on the root drive C:
Then open internet explorer, and call the html file as your link.
When you want to look at the next value, overwrite the html file. SO this way you only have one html file on the root of C: at a time, and are not accumulating them.
On the Form's On Close event, you erase the file.
Something like this:
'Without the declarations
Const ForWriting = 2
stText = "<html><head><title>New Page 1</title></head><body>Hello World</body></html>"
stLink = "C:\CurrentRecord.txt"
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.CreateTextFile(stLink) ' this will overwrite
Set objFile1 = objFSO.OpenTextFile(stLink, ForWriting)
objFile1.WriteLine stText
Set objExplorer = CreateObject("InternetExplorer.Application")
objExplorer.Navigate stLink
objExplorer.Visible = 1
This should work. It will open IE and show the contents of the file. I use IE and files to make Help systems for the apps I develop, but I usually make them in FrontPage. I will try this making pages on the fly (which some developers recommend.)
HTH
mmcdonal
|
