Lebans RTF Control install problem

  • Thread starter Thread starter zbud
  • Start date Start date
Z

zbud

trying to install this control from inside of Access 2003 using the
shellwait code found on the MVP's site.

Access just hangs until "not responding". After closing Access the
setup program runs although it takes 7-10 seconds at 100% before the
installshield wizard appears and then installs OK from there.

This is a Dell Laptop Pent 4 M, 1 gig ram, XP sp2.

Any thoughts ? My obkect is to insure the user gets the files installed
before attempting to use the form with the control on it.

Am I doing something wrong or is there a better way ?

Bud
 
Why are you trying to install if from inside the Access application?

Since registering is a one-time deal, it would make far more sense to use a
Bat file or VBScript when you're installing the application rather than
putting it into the application itself.
 
How can I be assured the users install the control, if the install is
outside of the application ?

Bud
 
You can't be, but you could check whether they have, and abort if they
haven't.

If you give them an installation package, odds are pretty good that they'll
use it.
 
you are probably right but I need to understand the shellwait module in
the event I need it in the future. Should I have been able to install a
package like the RTF from inside of Access 2003 ?

Bud
 
zbud said:
you are probably right but I need to understand the shellwait module in
the event I need it in the future. Should I have been able to install a
package like the RTF from inside of Access 2003 ?
Click to expand...

To be honest, I'm not sure whether you should have been able.

The fact that your application is using that control will mean that you're
going to have a References problem when you enter the application and the
workstation doesn't already have the control registered. That's going to
cause funky things to happen with any VBA code you run.

Better than Shelling to regsvr32.exe would probably be to use the
DllRegisterServer function.

You declare it as:

Declare Function DllRegisterServer Lib "<yourlib.ocx>" () As Long

Then simply call DllRegisterServer.
 
The Lebans RTF control does have an OCX but comes with a complete
install program, I don't know if registering the OCX is enough. This
shellwait call starts a setup.exe which in turns starts an
installshield installer.

Perhaps the question I should have asked is when Access checks the
references, when the app starts or the 1st time the control is used ?
if it's when the app starts then any installs needed should be run
before starting the program.

Thanks

Bud
 
zbud said:
Perhaps the question I should have asked is when Access checks the
references, when the app starts or the 1st time the control is used ?
if it's when the app starts then any installs needed should be run
before starting the program.
Click to expand...

The best explanation I've read on this topic is MichKa's
http://www.trigeminal.com/usenet/usenet026.asp

Bottom line is that if your application is missing any references, it can
affect code running anywhere at any point in using the application.
 
Back
Top