Diaplying HTML

[Alex]

I need to display html info on an Access form. To do this I am using
the Micorsoft Web Browser control which uses shdocvw.dll

The problem with this is that

a. the control is not resizable. Once it has been position on the form
it cannot be resized and needs to be deleted and then reinserted. but
more importantly if the user resizes a form the control cannot be
resized accordingly

b. there is no way of printing the contents of the html on a report

Does anyone know of an alternative compenent (dll or ocx) that I could
use to solve either of these issues.
Alex

[Lyle Fairfield]

Re: Diaplying HTML

Alex wrote:[color=blue]
> I need to display html info on an Access form. To do this I am using
> the Micorsoft Web Browser control which uses shdocvw.dll
>
> The problem with this is that
>
> a. the control is not resizable. Once it has been position on the form
> it cannot be resized and needs to be deleted and then reinserted. but
> more importantly if the user resizes a form the control cannot be
> resized accordingly
>
> b. there is no way of printing the contents of the html on a report
>
> Does anyone know of an alternative compenent (dll or ocx) that I could
> use to solve either of these issues.
> Alex[/color]

I resize as:

Private Sub Form_Open(Cance l As Integer)
Me.wbHDSBHelp.W idth = 480
End Sub

where wbHDSBHelp points to the Web Browser Control.

I'm not sure what you mean by "no way of printing the contents of the
html on a report" ... but you can print the html on the browser control
by right clicking and choosing print from the pop up menu.

I expect that with a little dickering one could grab the innerText or
innerHTML of the control and do whatever you wanted with it.

For any report you need a record source, ... or you can manipulate the
various methods of the report or even, in later versions of Access, its
recordset ... these last two do not seem to be extensively documented
and they can be tedious.



--
--
Lyle
--
From ADO28.chm

Deprecated Components
Each of the following components is considered obsolete. While these
components are still supported in this release of the Microsoft® Data
Access Components (MDAC), they may be removed in the future. When
writing new applications, you should avoid using these deprecated
components. When modifying existing applications, you are strongly
encouraged to remove any dependency on these components.

ODBC Provider (MSDASQL)
You are strongly encouraged to use one of the native OLE DB Providers
instead of the Microsoft Open Database Connectivity (ODBC) Provider.
Native OLE DB Providers provide better application stability and
performance. Furthermore, native OLE DB Providers will be supported in
the future, whereas MSDASQL will not have any new features added to it,
will not be available on 64-bit, and will not be accessible from the OLE
DB NET Data Provider.

Remote Data Services (RDS)
Remote Data Services (RDS) is a proprietary Microsoft mechanism for
accessing remote data across the Internet or intranet. Microsoft is now
shipping the Microsoft Simple Object Access Protocol (SOAP) Toolkit 2.0
that enables you to access remote data using an open, XML-based
standard. Given the availability of the SOAP Toolkit 2.0, you should
migrate from RDS to SOAP. The SOAP 2.0 Toolkit 2.0 also includes sample
code for remotely accessing Microsoft ActiveX® Data Objects (ADO)
Recordsets.

Jet and Replication Objects (JRO)
The Microsoft Jet OLE DB Provider and other related components were
removed from MDAC 2.6. Microsoft has deprecated the Microsoft Jet
Engine, and plans no new releases or service packs for this component.
As a result, the Jet and Replication Objects (JRO) is being deprecated
in this release and will not be available in any future MDAC releases.

.....

[Tom van Stiphout]

Re: Diaplying HTML

On 23 Feb 2005 05:17:33 -0800, alecjames1@hotm ail.com (Alex) wrote:

Be grateful that it works at all.

You could automate a browser window, but of course not inside a form.

-Tom.

[color=blue]
>I need to display html info on an Access form. To do this I am using
>the Micorsoft Web Browser control which uses shdocvw.dll
>
>The problem with this is that
>
>a. the control is not resizable. Once it has been position on the form
>it cannot be resized and needs to be deleted and then reinserted. but
>more importantly if the user resizes a form the control cannot be
>resized accordingly
>
>b. there is no way of printing the contents of the html on a report
>
>Does anyone know of an alternative compenent (dll or ocx) that I could
>use to solve either of these issues.
>Alex[/color]

[Paradigm]

Re: Diaplying HTML

The resize code does not work. The browser control stays at the size it was
inserted on the form. Have you tried it?

The printing issue relates to printing the html info on a report that also
contains other info. i.e. not just the html
Alex

"Lyle Fairfield" <lylefair@yahoo .ca> wrote in message
news:%L%Sd.4581 $If1.409658@rea d2.cgocable.net ...[color=blue]
> Alex wrote:[color=green]
> > I need to display html info on an Access form. To do this I am using
> > the Micorsoft Web Browser control which uses shdocvw.dll
> >
> > The problem with this is that
> >
> > a. the control is not resizable. Once it has been position on the form
> > it cannot be resized and needs to be deleted and then reinserted. but
> > more importantly if the user resizes a form the control cannot be
> > resized accordingly
> >
> > b. there is no way of printing the contents of the html on a report
> >
> > Does anyone know of an alternative compenent (dll or ocx) that I could
> > use to solve either of these issues.
> > Alex[/color]
>
> I resize as:
>
> Private Sub Form_Open(Cance l As Integer)
> Me.wbHDSBHelp.W idth = 480
> End Sub
>
> where wbHDSBHelp points to the Web Browser Control.
>
> I'm not sure what you mean by "no way of printing the contents of the
> html on a report" ... but you can print the html on the browser control
> by right clicking and choosing print from the pop up menu.
>
> I expect that with a little dickering one could grab the innerText or
> innerHTML of the control and do whatever you wanted with it.
>
> For any report you need a record source, ... or you can manipulate the
> various methods of the report or even, in later versions of Access, its
> recordset ... these last two do not seem to be extensively documented
> and they can be tedious.
>
>
>
> --
> --
> Lyle
> --
> From ADO28.chm
>
> Deprecated Components
> Each of the following components is considered obsolete. While these
> components are still supported in this release of the Microsoft® Data
> Access Components (MDAC), they may be removed in the future. When
> writing new applications, you should avoid using these deprecated
> components. When modifying existing applications, you are strongly
> encouraged to remove any dependency on these components.
>
> ODBC Provider (MSDASQL)
> You are strongly encouraged to use one of the native OLE DB Providers
> instead of the Microsoft Open Database Connectivity (ODBC) Provider.
> Native OLE DB Providers provide better application stability and
> performance. Furthermore, native OLE DB Providers will be supported in
> the future, whereas MSDASQL will not have any new features added to it,
> will not be available on 64-bit, and will not be accessible from the OLE
> DB NET Data Provider.
>
> Remote Data Services (RDS)
> Remote Data Services (RDS) is a proprietary Microsoft mechanism for
> accessing remote data across the Internet or intranet. Microsoft is now
> shipping the Microsoft Simple Object Access Protocol (SOAP) Toolkit 2.0
> that enables you to access remote data using an open, XML-based
> standard. Given the availability of the SOAP Toolkit 2.0, you should
> migrate from RDS to SOAP. The SOAP 2.0 Toolkit 2.0 also includes sample
> code for remotely accessing Microsoft ActiveX® Data Objects (ADO)
> Recordsets.
>
> Jet and Replication Objects (JRO)
> The Microsoft Jet OLE DB Provider and other related components were
> removed from MDAC 2.6. Microsoft has deprecated the Microsoft Jet
> Engine, and plans no new releases or service packs for this component.
> As a result, the Jet and Replication Objects (JRO) is being deprecated
> in this release and will not be available in any future MDAC releases.
>
> ....[/color]

[Stephen Lebans]

Re: Diaplying HTML

You cannot use the WebBrowser control on a report. I have not seen any
other HTML compatible ActiveX control that will work on an Access
Report.

--

HTH
Stephen Lebans

http://www.lebans.com

Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.


"Paradigm" <alecjames1@hot mail.com> wrote in message
news:Bc0Td.42$Y o1.10@newsfe1-gui.ntli.net...[color=blue]
> The resize code does not work. The browser control stays at the size[/color]
it was[color=blue]
> inserted on the form. Have you tried it?
>
> The printing issue relates to printing the html info on a report that[/color]
also[color=blue]
> contains other info. i.e. not just the html
> Alex
>
> "Lyle Fairfield" <lylefair@yahoo .ca> wrote in message
> news:%L%Sd.4581 $If1.409658@rea d2.cgocable.net ...[color=green]
> > Alex wrote:[color=darkred]
> > > I need to display html info on an Access form. To do this I am[/color][/color][/color]
using[color=blue][color=green][color=darkred]
> > > the Micorsoft Web Browser control which uses shdocvw.dll
> > >
> > > The problem with this is that
> > >
> > > a. the control is not resizable. Once it has been position on the[/color][/color][/color]
form[color=blue][color=green][color=darkred]
> > > it cannot be resized and needs to be deleted and then reinserted.[/color][/color][/color]
but[color=blue][color=green][color=darkred]
> > > more importantly if the user resizes a form the control cannot be
> > > resized accordingly
> > >
> > > b. there is no way of printing the contents of the html on a[/color][/color][/color]
report[color=blue][color=green][color=darkred]
> > >
> > > Does anyone know of an alternative compenent (dll or ocx) that I[/color][/color][/color]
could[color=blue][color=green][color=darkred]
> > > use to solve either of these issues.
> > > Alex[/color]
> >
> > I resize as:
> >
> > Private Sub Form_Open(Cance l As Integer)
> > Me.wbHDSBHelp.W idth = 480
> > End Sub
> >
> > where wbHDSBHelp points to the Web Browser Control.
> >
> > I'm not sure what you mean by "no way of printing the contents of[/color][/color]
the[color=blue][color=green]
> > html on a report" ... but you can print the html on the browser[/color][/color]
control[color=blue][color=green]
> > by right clicking and choosing print from the pop up menu.
> >
> > I expect that with a little dickering one could grab the innerText[/color][/color]
or[color=blue][color=green]
> > innerHTML of the control and do whatever you wanted with it.
> >
> > For any report you need a record source, ... or you can manipulate[/color][/color]
the[color=blue][color=green]
> > various methods of the report or even, in later versions of Access,[/color][/color]
its[color=blue][color=green]
> > recordset ... these last two do not seem to be extensively[/color][/color]
documented[color=blue][color=green]
> > and they can be tedious.
> >
> >
> >
> > --
> > --
> > Lyle
> > --
> > From ADO28.chm
> >
> > Deprecated Components
> > Each of the following components is considered obsolete. While these
> > components are still supported in this release of the Microsoft®[/color][/color]
Data[color=blue][color=green]
> > Access Components (MDAC), they may be removed in the future. When
> > writing new applications, you should avoid using these deprecated
> > components. When modifying existing applications, you are strongly
> > encouraged to remove any dependency on these components.
> >
> > ODBC Provider (MSDASQL)
> > You are strongly encouraged to use one of the native OLE DB[/color][/color]
Providers[color=blue][color=green]
> > instead of the Microsoft Open Database Connectivity (ODBC) Provider.
> > Native OLE DB Providers provide better application stability and
> > performance. Furthermore, native OLE DB Providers will be supported[/color][/color]
in[color=blue][color=green]
> > the future, whereas MSDASQL will not have any new features added to[/color][/color]
it,[color=blue][color=green]
> > will not be available on 64-bit, and will not be accessible from the[/color][/color]
OLE[color=blue][color=green]
> > DB NET Data Provider.
> >
> > Remote Data Services (RDS)
> > Remote Data Services (RDS) is a proprietary Microsoft mechanism for
> > accessing remote data across the Internet or intranet. Microsoft is[/color][/color]
now[color=blue][color=green]
> > shipping the Microsoft Simple Object Access Protocol (SOAP) Toolkit[/color][/color]
2.0[color=blue][color=green]
> > that enables you to access remote data using an open, XML-based
> > standard. Given the availability of the SOAP Toolkit 2.0, you should
> > migrate from RDS to SOAP. The SOAP 2.0 Toolkit 2.0 also includes[/color][/color]
sample[color=blue][color=green]
> > code for remotely accessing Microsoft ActiveX® Data Objects (ADO)
> > Recordsets.
> >
> > Jet and Replication Objects (JRO)
> > The Microsoft Jet OLE DB Provider and other related components were
> > removed from MDAC 2.6. Microsoft has deprecated the Microsoft Jet
> > Engine, and plans no new releases or service packs for this[/color][/color]
component.[color=blue][color=green]
> > As a result, the Jet and Replication Objects (JRO) is being[/color][/color]
deprecated[color=blue][color=green]
> > in this release and will not be available in any future MDAC[/color][/color]
releases.[color=blue][color=green]
> >
> > ....[/color]
>
>[/color]