Problem with Treeview Control & Toolbar

  • Thread starter Thread starter Kevin
  • Start date Start date
K

Kevin

Hi all

I have a few problems with my Access 2000 application that
I wrote.

1.I have added a Microsoft Treview control version 6.0
control to my form to simulate an explorer treeview so
that users can select a folder to export the database
tables to. Well When I'm in Access 2000 the treeview
control works exactly like I want it to. BUT, when I
install it on a machnie that has Access Runtime, the
control appears, but when I want to click on a node, it
does not expand. I do not understand why it does not do
this. I am pretty sure that I have included the correct
OCX's (I included both MSCOMCTL.OCX and MSCOCT2.OCX) but I
cannot find any help on this, and it is quite crucial to
my app. If no one can help me, what else would you suggest
as a work around? Also I have created the package in
Windows XP and am trying to run it on Windows 98. Also I
have re-installed the Access runtime, but I still get the
same problem. I have also installed Office SP3

2. In Access 2000 Runtime, I see that there is no toolbar,
why is this? Do I have to create my own toolbar and use
the docmd command to carry out the operation of the button?

TIA for any help

Kevin
 
Did you use the P&D wizard to depoly your application? Normally, the P&D
wizard will pick up all controls and dependencies ... I've deployed the
treeview control several times (although never with runtime) and had no
trouble IF the end user installed correctly.

This is from the MS website regarding the differences between retail and
runtime Access:

In the runtime version:

- The Database, Macro, and Visual Basic Environment windows are
hidden, and all Design views are hidden, including the Filter windows.
- Built-in toolbars are no supported, but you can add custom toolbars
to your application.
- Your application uses its own Help file.
- Some windows, menus (including shortcut menus), and commands are
hidden or disabled.
- Visual Basic error handling is required. Errors that are not handled
by your code will shut down the application without warning. For this
reason, the use of macros is not recommended.
- Certain keystrokes and key combinations are disabled.

So the answer re: toolbars is Yes, you must build your own.
 
Back
Top