Hi again Ken, I did have another look at it, and I see there's a lot more which can be said, including as you mentioned, discussing what info can come out of the accessible object. I am right now starting to collect examples of how others have used MSAA events or info in their apps to make something work, so I can present them in one unified class, which picks up where #18 left off. Thanks for the idea. Chip
_____ From: Scott, Ken [mailto:[email protected]] Sent: Friday, October 07, 2011 2:42 PM To: '[email protected]' Subject: RE: Three Issues/Questions for Scripting Window-Eyes with Microsoft Access 2010 Database Program Chip, I am all too aware of time limitations. I will review class 18 again over the weekend and get back to you if I think another class on accessible object will be worthwhile. Ken From: Chip Orange [mailto:[email protected]] Sent: Thursday, October 06, 2011 7:02 PM To: [email protected] Subject: RE: Three Issues/Questions for Scripting Window-Eyes with Microsoft Access 2010 Database Program Scott, sorry I'm not able to answer all your questions tonight, I'm just out of time. The one about the accessible object is really part of a much bigger topic: using MSAA info. I'll write up another class on this if you want a class; there is one (class #18) which covers just the beginnings of using MSAA, but the question you're asking may not be answered in class 18; it may take another class. So, after you've had a look at 18, let me know if you need another MSAA class. Also, if you're using XP, note that there is a known problem with MSAA under XP, so that some programs don't send proper MSAA information. That means you just may get blank information when you try this. I don't know how MS Office 2010 works under XP, if it's MSAA is ok or not; I suspect it will be ok. hth, Chip _____ From: Scott, Ken [mailto:[email protected]] Sent: Wednesday, October 05, 2011 1:10 PM To: '[email protected]' Subject: Three Issues/Questions for Scripting Window-Eyes with Microsoft Access 2010 Database Program Hi gw-scripting list members, I am attempting to improve the usability of the Microsoft Access 2010 database program with Window-Eyes. I am not a programmer of any kind let alone an object oriented one. I have done some analysis of the Access 2010 and Window-Eyes combination. I also listened to all of the podcasts and read all of the documentation that I thought applied to what I am trying to do. I am left with three issues/questions. One thing that I am trying to do is to automatically maximized the Access 2010 windows. The problem is that I am getting two object.classnames for what appear to be the same object depending on what analytical tool or approach that I use. If I use, Gw Micro's Window Manager to check on classnames for objects, I get one result. If I use the Object Browser in Chip Orange's Microsoft Word based development environment, I get another Classname. For example, in Window Manager there is a OTable classname, whereas, in the Object Browser, there is a table classname. Can anyone suggest which version of the object classname that I should try first when scripting to maximize the windows? The second problem that I am having is determining the syntax to load set files based on off screen events. I plan to use the presence of Access window objects plus view button status to load set files. My first issue. What is the property/method to load a specified set file? I did write GW Micro Support asking about this situation. I was told about the window.loadset object. Unfortunately when I check the Window-Eyes developer reference, this object appears to tell if a set file is loaded and not to load a set file. Second, what is the syntax for using an accessible string as part of an operation. I can find a long string that gives the name of a view button and its pressed verses unpressed status in my analysis. I do not know how to write this into an operation. My tentative idea for a syntax is something like: If window.classname = OTable and Datasheet view status = pressed then loadset.TableDatasheetView. If anyone can suggest how precisely the above hypothetical operation should be written I will be forever in your debt. The third area of trouble is in reclassing a custom control. If I understood the Window-Eyes developer reference correctly, I need to use the type object to reclass the object. I will need to first use the retrieve property to place the custom control into my script. I then need to use the set property plus the type to reclass the custom control. If the custom control is okttbx and need to be reclassed to an editbox, what would these operations look like? If I have confused you, please send me any follow up questions that you have. Regards, Ken Scott
