Pete,
Googling here so someone else may have chipped in.
It's not the case AFAIK in 97 at least (and I presume the other
versions too). It's part of mscomctl.ocx but the base version of
Access doesn't support the control (or other controls such as
statusbar and ListView etc that are in the mscomctl.ocx). The ODE
supports mscomctl.ocx.
On most PC's I've come across mscomctl.ocx is already registered. It's
just Access isn't licenced to use the controls.
I've gotten around this by wrapping the treeview in a VB ocx (adding
some of my own methods and properties along the way like a quick clear
using API calls). This is easy to do (there's even a wizard in VB6 to
do it for you! (But as per usual you'll need to clean it up)).
The only control you can't wrap in this way is the datagrid (legally
that is). Unless of course this has changed (anyone know?)
Of course you'll now have to make sure the versioning is A-OK with the
ocx but if you are in a corporate enviroment this can be controlled.
Just remember to compile your project with 'Project compatibilty' when
developing and 'Binary compatibility' when it's ready to go (well as
rule of thumb anyways).
Regards,
Peter
"(Pete Cresswell)" <x@y.z> wrote in message news:<n2******* *************** **********@4ax. com>...
RE/How can I transfer across the tree control to client? Is there a dll which I
can just copy and register using regsvr32?
Do you know for sure that it isn't on the client's PC already?
I'm just starting to dabble with the TreeView control and I'm going on the
assumption that it's part of the base MS Access install.
Somebody say something if this is not the case.