19-11-19 01:48 PM
Hi,
I'm currently working on Microsoft Access Application Form automation.
Everything works fine, I'm able to attach the application, spy element by using AA Mode but as soon as I need to highlight the element, it can take 2 minutes to find the element in the application, and the slowness is the same when I use the navigate stage(e.g. Global Mous Click Centre).
I know the reason, there's a lot of element in this MS access application (over 800) , so I've tried many combinations of attributes in the application modeller to optimize the search. Match index is always 1 for every element and ordinal as well. (Picture 1).
My solution will be to point directly to an element by getting his ancestor from InspectTool (Picture 2), but so far I'm not sure it's possible to do that.
Does anyone has already facing to that kind of problem?
Picture 1
Picture 2
20-11-19 07:58 AM
MS Access GUI can be quite slow to spy and having 800 elements on screen can surely be slow, have you tried UI Mode?
If you;re getting data you can try connecting to it using OLEDB, You can also run queries but that can be risky.
20-11-19 12:40 PM
20-11-19 08:42 PM
21-11-19 04:05 AM
21-11-19 12:31 PM