missing msflexgrid.ocx

  • Thread starter Thread starter Tom Jackson
  • Start date Start date
T

Tom Jackson

I created a form on my development machine (which has everything in the
world installed) and dropped a flex grid on the form. When I take the .adp
to the end user's machine the form won't run. The end user's machine does
not have the msflexgrid.ocx installed.

I found the msflexgrid on my development machine, installed and registered
it on the end-user's machine -- still no go -- it complains about license.

Is msflexgrid.ocx not distributable?
If it is, how do I distribute it?
If it is not, how do I make use of the code I already wrote? i.e. Where can
I buy a 3rd party tool compatible with msflexgrid?
Where did it come from on my development machine? (visual studio? VB? Office
Developer? SQL SERVER?)
How do I avoid the problem in the future -- how do I know which of the
thousands of activeX controls in my "More Controls" dropdown are really
usable?

Any help would be appreciated!
 
Ahh, the joy of distribution. It's a joke around my
office- "works great on my machine".
I found the msflexgrid on my development machine, installed and registered
it on the end-user's machine -- still no go -- it
Click to expand...
complains about license.
This I've never seen. I didn't see anything in the KB
that looked like this either. MSFlexgrid.ocx is
distributable ASIK (sure hope it is) and I can't remember
exactly what it gets installed with, VS6 for sure though.
You may want to try regsvr32 "C:\Windows\System32
\MsFlexgrid.ocx" -u to unregister it, copy a new one in
and re-register it. There may be a dependancy with
another control library such as MSCOMCTL that I don't
know about. You may have an issue if the target machine
is an older OS. Just things to think about.
How do I avoid the problem in the future -- how do I know which of the
thousands of activeX controls in my "More Controls" dropdown are really
usable?
Click to expand...

You don't. You never can and never will. It's part of the
fun! You need to distribute apps with the dependant
components and conditionally install them and/or force
the end user to do things like upgrade IE. Some special
things will be obvious - if Office isn't installed the
Word object library obviously isn't either, on top of
that, if you use Office XP you've got Word 10.0
libraries, what if the user has Office 2K, or help us,
97? Others are even more tricky - what version of
MDAC/ADO does the user have? Depends. How do you know
some other 3rd party app didn't install a component
before you did? You don't. This is why you use the VB P&D
wizard or Wise or InstallShield for distribution.
HTH - distribution can be even more difficult than
development.
Ben
 
Back
Top