R
Ron Weiner
I have never used a WebBrowser control in an Access App, but I do have one
commercial VB app that uses it. We have had success with hundreds (probably
thousands by now) of users that have been able to use the application
without ANY kind of install.
Our minimum requirements for the application are Win2K and higher, IE-4 and
higher and an available USB port. The Win2K and higher requirement insure
that the VB6 runtime is there, and the IE-4 and higher requirement insures
that the WebBrowser control is available. The app is distributed on a USB
flash memory drive and often times is run directly from there without any
kind of installation being performed on the host computer.
Soooo....
1, Yes but not in Access
2, I haven't the faintest.
3, It is IMHO neither a good or bad thing, but an "All Right" thing.
4, To date we have not had a single issue. How many PC's running windows do
you think are out there that do not have IE installed. I suspect not to
many.
5, If I needed some functionality that the WB control provides that I could
not get using native Access controls I'd use it.
commercial VB app that uses it. We have had success with hundreds (probably
thousands by now) of users that have been able to use the application
without ANY kind of install.
Our minimum requirements for the application are Win2K and higher, IE-4 and
higher and an available USB port. The Win2K and higher requirement insure
that the VB6 runtime is there, and the IE-4 and higher requirement insures
that the WebBrowser control is available. The app is distributed on a USB
flash memory drive and often times is run directly from there without any
kind of installation being performed on the host computer.
Soooo....
1, Yes but not in Access
2, I haven't the faintest.
3, It is IMHO neither a good or bad thing, but an "All Right" thing.
4, To date we have not had a single issue. How many PC's running windows do
you think are out there that do not have IE installed. I suspect not to
many.
5, If I needed some functionality that the WB control provides that I could
not get using native Access controls I'd use it.