Another post on Listview control properties

Another post on Listview control properties

Anonymous
Not applicable
274 Views
3 Replies
Message 1 of 4

Another post on Listview control properties

Anonymous
Not applicable
I'm using Acad2002. I have a form with a listview control. In the code, I change the left, top, height, width and name properties. It works fine on the development system but when I deploy it to the workstations, they get a "Compile Error" - "Method or data member not found." The debugger highlights the properties that it's having a problem with. I comment these lines out and it compiles. I break where the listview control gets initialized and look through Watch and expand the listview control. I can see all the properties associated with this control, even the ones I'm getting compile errors on - height, top, left, width and name etc. Any clue as to why I cannot change these properties in the code when they are an obvious part of the object? The references used and checked on the workstation are the same as whats on the development system. I'm really baffled. Thanks for your response. Brent
0 Likes
275 Views
3 Replies
Replies (3)
Message 2 of 4

Anonymous
Not applicable
Are you using VB or VBA ?
0 Likes
Message 3 of 4

Anonymous
Not applicable
VBA "thenrich" wrote in message news:27071485.1079449792565.JavaMail.jive@jiveforum2.autodesk.com... > Are you using VB or VBA ?
0 Likes
Message 4 of 4

Anonymous
Not applicable
I figured it out finally! It turns out that I'm using a multi-page control and it defaults to having 2 pages. In the original design, I've deleted the second page and it gets built at run time if needed. The listview control is on the first page and it too is duplicated on to the second page if needed. When I deployed the form to the workstations, the "Complie error - method or data member not found" was coming up when the listview properties were being addressed. Through many hours of checking dll and ocx versions, and even installing VB on a workstation which didn't make a difference, I began playing around in VBAIDE and I figured out that if I viewed the form object in VBAIDE on the workstation and then closed VBAIDE and ran the program it worked fine. I was able to programmatically change and address the properties that were giving me errors. Obviously viewing the form caused something to get straightened out. Hope this helps someone else. Brent "Brent" wrote in message news:40574b07$1_1@newsprd01... > VBA > > "thenrich" wrote in message > news:27071485.1079449792565.JavaMail.jive@jiveforum2.autodesk.com... > > Are you using VB or VBA ? > >
0 Likes