Arthur Fuller
artful at rogers.com
Mon Dec 22 15:54:05 CST 2003
IME Drag & Drop is quite tricky and a solution to a given problem is problem-specific. I have given this problem much thought and have failed to come up with a generic solution (although I recognize that in theory at least, with enough parameters a function could do it). I have for example a treeview thing that is based upon the Switchboard -- a single table. I have seen an example (in PowerBuilder not Access) where you can drag an employee from one dept. to another; this is doable but not not generalizable, IMO. If we had function pointers in Access, the solution would be a lot easier, but faking them is a complex problem in itself. I would suggest that you copy and clone the basic treeview code and then supply the specifics that you need in each given instance. That's the only way I've been able to make it work. Could easily be that I don't understand enough about overriding the core methods, but if so then I don't, so I have found the simple path to a working solution is to clone and override locally. Ungraceful, I admit, but Access doesn't offer inheritance so I did what I could make work. Incidentlly, lest you get the impression that I'm an expert on treeviews, I have yet to master the icon part of it. I'm totally baffled by that stuff. Arthur -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Julie Reardon-Taylor Sent: Monday, December 22, 2003 9:05 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Tree View Control Arthur, Are you on today? I downloaded Arthur's example, but would also like the capability to drag and drop. Found some info on the MS-Knowledgebase, but need some more guidance. Anyone have some experience with this? The article uses one table to update the fields after dragging and dropping, and I want to populate the parent and child fields with two different tables linking them on an ID. I'm afraid that using a querydef will not allow the tables to update. Would it be best to load two recordsets and populate the tree nodes that way? Not sure if the tree view control will allow drag and drop using data from two separate tables. Why did MS use one table for the parent and child nodes? The link for the MS-Article is here: http://support.microsoft.com/default.aspx?scid=kb;en-us;209898&Product=a cc Julie Reardon-Taylor PRO-SOFT OF NY, INC. www.pro-soft.net _________________________________________________________________ Worried about inbox overload? Get MSN Extra Storage now! http://join.msn.com/?PAGE=features/es _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com