1

Topic: TreeView without MSCOMCTL.OCX. All on VBA (Approaches for Access 64-bit)

Here on a site JKP Application Development Services Found article An MSForms (All VBA) Treeview Introduction In it it is written about creation of analog TreeView without usage OCX. Examples in source codes for Access (mdb), Excel and Word are laid out.
It is written that development is checked up for
Excel 2000
Excel 2003
Excel 2010
Excel 2010 (64 bit)
Excel 2011 (MAC Office)
Excel 2013 (32 bit)
Access 2003
Access 2010 (32 bit)
Access 2010 (64 bit)
I downloaded to myself an example for Access. Launched in Access 2010 (32 bits) Beautifully. Truth is any glitch in AutoExec. At me the error 13 Type mismatch took off. But at form start frmDemo no errors existing.
Now I sit, I understand. Probably it is quite good alternative TreeView. Especially if you write the general-purpose programs for 32-h/64 bit Offices.
The downloaded example I do not put, since its size (280) exceeds the resolved.
Can to whom it is useful.

2

Re: TreeView without MSCOMCTL.OCX. All on VBA (Approaches for Access 64-bit)

Joss wrote:

there is any glitch in AutoExec. At me the error 13 Type mismatch took off.

So these woodpeckers  in a macro condition check

[CurrentProject]. [Application]. [Version] <=12

And that CurrentProject]. [Application]. [Version], , has string type, it nobody told...
In general, it is enough  value to which it is compared (in both conditions).

3

Re: TreeView without MSCOMCTL.OCX. All on VBA (Approaches for Access 64-bit)

Mda-and-a-a... . Did not check up search. I am sorry.

4

Re: TreeView without MSCOMCTL.OCX. All on VBA (Approaches for Access 64-bit)

Akina wrote:

it is passed...
So these woodpeckers  in a macro condition check

[CurrentProject]. [Application]. [Version] <=12

And that CurrentProject]. [Application]. [Version], , has string type, it nobody told...
In general, it is enough  value to which it is compared (in both conditions).

Personally I preferred to make so

Val ([CurrentProject]. [Application]. [Version]) <=12

Me here interested, why in both cases of a condition not the strict?> = and <=?

5

Re: TreeView without MSCOMCTL.OCX. All on VBA (Approaches for Access 64-bit)

Joss wrote:

Personally I preferred to make so

At first, unreasonably. String - more general-purpose type.
Secondly, generally it is simply wrong. It is good that in MS Access a separator of discharges of subversions - a point, it is good that is not present () such version, as 12.1...

6

Re: TreeView without MSCOMCTL.OCX. All on VBA (Approaches for Access 64-bit)

And what you tell here on their this work of art?

Private Sub Form_Load ()
If Application. Version> = 12# Then
Me. Filter = "HelpID=1"
Else
Me. Filter = "HelpID=2"
End If
Me. FilterOn = True
End Sub

the Form frmHelp. Besides 13 Type Mismatch

7

Re: TreeView without MSCOMCTL.OCX. All on VBA (Approaches for Access 64-bit)

Joss wrote:

Personally I preferred to make so

Val ([CurrentProject]. [Application]. [Version]) <=12

it is More correct than Val () function Csng () works. To it all the same, what separator (.) or () , but here in a macro she refuses to work, and Val () works.