Convert tree view to Late Binding using Microsoft Windows Common Controls 6.0 (SP6)

I'd agree with Daniel.

Also, the biggest reason to use Late Binding is to avoid reference issues. Since you MUST ensure that the control is available on the target machine there's little reason to use Late Binding for something of this nature.

Alright... got the code attached now. Will review  https://www.jkp-ads.com/articles/treeview.asp. Still would be interested in how I would convert this code though. It is pretty simple/clean.

I am wanting to change to late binding on these as I am getting 'random' errors in my accde on other user's machines. The files are in a trusted location, I have imported all objects into a new accdb and complied with no errors. These has to be something in reference to these additional references I had to pull in.

I use DAO and normally use Microsoft DAO 3.6 Object library but using Microsoft Office 15.0 Access Database engine object library as this was by default and my code appears to be working. Any preference on which to use?

Anything 2007+ should use Microsoft Office XX.X Access Database engine object library

Noted on late binding using the Active X. Also thanks for the optional tree view solution.

I am currently experiencing 'random' errors in some user machines when I convert to accde. I have created another application on users machines with no errors. I am suspecting it is my tree view that is causing this 'error'.

ActiveX controls are always suspect in situations like this. When I have to use them, I always create an installer that includes the controls needed, and allow that installer to determine if I need them or not.

Alright I was able to integrate his solution to replace the ActiveX tree I was using.

The last bit of code I need to figure out is how I can select a node in the tree if i pass a Key value???

I have been hacking around but not finding anything.

Hi Stephen,

You'd be better off asking this as a new question