Thanks Cetin!

That explains why it was not working. I was using the wrong events in trying it out on my own. I haven't looked at the solution app in some time - I guess it's time to pull it up again! :o)

Tracy



>>Is it possible to drag an item from a treeview control and drop it onto another treeview control or row in a grid and run a process based on the item dropped onto that control (the 2nd treeview or the row in the grid)?
>>
>>My goal is to allow users to 'match' two records in separate tables. I have an import process that updates records in multiple tables but since the data comes from a third party there are always exceptions that must be handled manually. The user scrolls a grid with records from table 1 (the imported data) and must match them to the appropriate record in table two (the existing data). Two grids or listboxes won't work because I need the ability to show hierarchy in the 2nd table so I am using a treeview which works great. I currently have code in the nodeclick event that stores the current user's selection in the treeview in a form property so I can tell which item in the treeview the user selected. I could just add a command button to update the data in the currently selected treeview node's appropriate record with the data in the records belonging to the currently selected record in the grid, but I would like to be able to allow the user to 'drag and drop.'
>>
>>

>>Table 1 Imported      Table 1's child table (only table one shown on a grid)
>>LastName              key
>>SSN                   policy number
>>parentkey             effective date
>>
>>Table 2 Existing      Table 2's child table (child nodes on table 2 parent in treeview)
>>LastName              key
>>SSN                   policy number
>>parentkey             effective date
>>

>>
>>The user sees table 2 parent as parent nodes in the treeview and table 2's child table's records as child nodes of table 2 records. There is a relationship setup between table1 and table1child and table2 and table2child of course. Table 1's record will update the values in table2's record.
>>
>>Basically, the user will look for a matching lastname and policy number in the treeview for each record in the grid (lastname only shown in grid) which displays the exceptions (policy number and other information required for matching the imported record to an existing record is shown elsewhere on the form.) I will probably switch it to two treeviews instead so the look and feel is consistent between the two tables.
>>
>>Any ideas?
>>
>>TIA! :o)
>>Tracy
>
>Tracy,
>It's easier to make it work between 2 TVs o a TV and a grid than making it to work on a single TV.
>Solution.app has sample showing DD between 2 TVs.
>Check UT magazine June 2001 issue making it in single TV as well. For dropping on grid remember you'd use OLE* dragdrop events (not directly dragover, dragdrop ...)
>Cetin