Hi,
This is the second posting for this. So any help is appreciated.

 I have redesigned a db and remade runtime versions accordingly. I have
uninstalled
and reinstalled it on another machine each time I have remade this. With an
earlier version
certain activex controls, like richtx worked. On later installs after
remaking the runtime version the same form and controls would not load. Any
thoughts. Any input is much appreciated. I used regsvr.exe to re-register
ocx.
Thanks again
Alan Schwartz

I have had both of these issues.  Access Slow to start runtime - yepper....
Access 97 runtime seems to load slow.  What I have done is put a shell
command as far to the top of startup as I can.  Then once the code is loaded
it uses win api to findout the shell application ( an animated GIF or
something) and close it.  It's a work around but it does work a little
better.

Since you are concerned about the literal load here's another idea.   An
even better way would be to write a VB app (.exe ) the starts up and does
the shell to start access runtime rather than starting access directly.
That way there is no wait for Access at all.  You could still let access
kill the VB app once it's loaded.  Doing this however will take a little
adjustment in your setup program so it runs the vb app instead of access.
You will also have to use something like the windows api findwind ( I forget
the exact name) so your can get the handle for the vb exe.

Regarding your issues with OCX's.  I have had exactly the same problem
myself many times.  I have not found a solution but have found some hints.
First thing to note is that Access mde ( if that is what you plan to use)
can compound the problem because it catches things compile does not ...
especially ActiveX reference problems.  Aside from mde's I have found
certain objects to have more problems than others.  in fact some never have
problems.  The richText I have found to have the same problem. The progress
bar is the worst.  Farpoints tabpro has the problem too.  I have an animated
GIF that works, but if any changes are made to the form .... anything, even
an open and resize.... it has to be removed and replaced on the form...
(same name or code will be lost).

What I have done is crude.. Everytime I have a problem like this I put it in
a sections of a function called debuglog.  It contains a list of my
experiences along this line.  When I do a mde I almost always have a problem
dealing witht the same controls.  So I go to each form that uses them and
open them and see if the control is there.  Usually is shows up blank.  The
code is still there, so I remove the control and replace it with the same
name.  That's all it takes.  Since my applications are large and contain may
forms I find this to be very time consuming and frustrating.