ListView Version Problems

[Jonathan]

This one is really, really annoying me. I know it's based around MS Access, but I'm posting it here since it is all to do with ActiveX controls.<br><br>I while back I developed an app in Access 97, and made extensive use of the ListView control v5.0 SP2 as supplied with the Microsoft Office Developer Edition Tools. I used the setup program to release this app along with the required OCX files and DLLs. This worked fine, and the app has been in use for three months with no problems.<br><br>Recently, one of my users installed MS Publisher on his PC.&nbsp;&nbsp;This upgraded the Microsoft Common Controls, which includes the ListView control to v6.0 SP3.&nbsp;&nbsp;I have also installed Visual Basic 6 on my machine, with the same effect.<br><br>Now I find that along with some annoying changes to DAO Recordsets, I am having many problems with the listview.&nbsp;&nbsp;It still works fine until I try and make any changes to the app.&nbsp;&nbsp;Then on my PC, when I try and access the Column Headers tab on the property pages, I get a fatal Dr Watsons error and it all goes a bit wrong.&nbsp;&nbsp;I discovered that by cutting the control and then pasting it back onto the form, I can prevent this from happenning.&nbsp;&nbsp;However, when I make my changes (which work fine on my computer) and release them onto any of my users PCs, including the ones who haven't done anything to their computers, it doesn't work.&nbsp;&nbsp;In runtime access, which is what they all use, when they try and open a form with a listview control on it, nothing happens (no errors or anything).&nbsp;&nbsp;In full access, I have seen various errors, such as &quot;There is no object in this control&quot;, or &quot;Method or Property of Object not found&quot;.<br><br>I have tried editing the forms on my users PC, but since the control was only installed on their computer by the setup program I created, I just get a message informing me that the control is not licensed.<br><br>So can anybody make any suggestions at all, please! One thing I am particularly interested in: at the time, I made the assumption that adding OCX files to the setup program would mean that they would be registered on the users computer when the setup program runs.&nbsp;&nbsp;I thought that this was fair enough, since I know that when you add OCX/DLL files, the setup wizard scans the dependency file if present, so it must recognise that the file needs registering.&nbsp;&nbsp;Is this true?<br><br>Please post anything you think might be relevent - it might give me some new ideas to work on if nothing else!<br><br>Thanks. <p> Jonathan<br><a href=mailto:j.w.george@virginnet.co.uk>j.w.george@virginnet.co.uk</a><br><a href= > </a><br>Working with: Visual Basic 6, Access 97, Visual Interdev 6, VBScript, Active Server Pages, SQL Server 6.5, Oracle 7

 

[MikeLacey]

Jon,<br><br>Could you try installing VB6 Service Pack 4? <p>Mike<br><a href=mailto:michael.j.lacey@ntlworld.com>michael.j.lacey@ntlworld.com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>