ContributionsMost RecentMost LikesSolutionsRe: Access change? I figured it out. My helpfu was weak. All was finding were articles on testing the DB applications. A second search brought up the article on the issue of having TC x64 and Office x32 and how to resolve it by installing the different Access engine. I the access install and now TC comes up in x86 mode and I can use the query again. Access change? Was there a change in Access 2016/Office 365? This query works fine on the PC with Access 2010 installed. #Create query Qry = ADO.CreateADOQuery() Qry.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;" + \ "Data Source="+mySource #Specify the SQL expression Qry.SQL = "Select * FROM [String_Table] WHERE [String_Table].[RID] = :Num" #Specify Parameter Value Qry.Parameters.ParamByName("Num").Value = rid #Execute the query try: Qry.Open() except RuntimeError: Log.Warning("Unable to find database " + str(mySource) + " aborting test run.") return "Abort" On the PC with with Access 2016/Office 365 the same project returns the Runtime error. SolvedRe: How to get the Excel sheet names using OLE object python testcomplete I had the same issue, the forum topics such as https://community.smartbear.com/t5/TestComplete-Functional-Web/how-to-check-if-sheet-in-excel-driver-exist-or-not/td-p/104645 gave me a pointer or two but didn't really answer my question. Though a bit of trial and error I arrived at: def Main(): #Routine to get list of worksheets from a work book #Location of workbook myResult = "C:\\Test_Development\\TR3462\\TR3462.xls" testCase = "TEST70204" #Open the new Excel workbook and sheet excel = Sys.OleObject["Excel.Application"] workBook = excel.Workbooks.Open(myResult) try: workSheet = workBook.Sheets.Item[testCase] except (RuntimeError): Log.Warning("Worksheet " + testCase + " was not found."); numFound = workBook.Sheets.Count Log.Message("This workbook has " + str(numFound) + " worksheets.") for i in range(0,numFound): sheetName = workBook.Sheets.Item[i+1].Name Log.Message(str(sheetName)) excel.Quit(); I hope that will help Manual test fontsDoes anyone know a good font to use when using Czech or Polish characters in the Manual test editor? The Manual test editor will show the correct character, however when exporting to Word or showing the step in the Manual test interface the characters do not display correctly.Re: Just Updated to TC 10.40 -- Can No Longer Open Manual TestsAgreed, Manual Tests and the ODT are two of the main reasons that we use TestComplete.Re: Just Updated to TC 10.40 -- Can No Longer Open Manual TestsI had this issue too. I've submitted a report to Technical Support as well.Re: TestComplete and QMLWill do, using Tanya's suggestions we've gotten deeper into the application but not quite deep enough so we'll see how it goes.Re: TestComplete and QMLThank you for the update Tanya and I'll look into the other options suggested.TestComplete and QMLI know the question has been asked a few times, but is there an update for supporting the testing of Qt QML in TestComplete 10?SolvedRe: Name Property valus issue with Unicode(Japanese Character)Check this thread