Custom Query (3933 matches)

When i try to execute the following statements in autoit, it is retrieving wrong values from database, could any one help.

$sqlCon = objCreate("ADODB.Connection")
$objRecordSet = ObjCreate("ADODB.RecordSet")
$sqlCon.Open("Provider='IBMDA400';Data Source = '10.0.1.25';User Id='USERNAME'; password='Password';")
$oRs = $sqlCon.Execute("select * FROM ccdata.rcmast where MSACT# = '8217'")
MSGBOX(0,"",$oRs.Fields("MSACT#").value)

Expected values is 8217, whereas it is retrieving 6213.

I tried using VBseditor for executing the above statement, vbseditor is retrieving correct from database whereas autoit is displaying wrong values.

* Settings * Suite Setup Library AutoItLibrary

* Test Cases * PACS Service Admin

[Setup] Launch PACS Service Admin

* Keywords * Launch PACS Service Admin

AutoItLibrary.Run C:
Program Files (x86)
PACS Service
PACS Service Administration.exe

In the PACS Service directory there are a couple of EXE files.

PACS Service Administration.exe PACS Service.exe

When I run the test case as it I get an error "Windows Service Start Failure"...

If I modify or remove the word service from the PACS Service Administration.exe and change the test case, then it runs as expected. If I leave PACS Service Administration.exe as is, and modify or remove PACS Service.exe, then the application launches but the test case does not finish. Seems like it is waiting for something.

Autoit crashes frequently when run on the checked build of Windows. The crash occurs when the process is shutting down. Investigation showed that the crash is due to an unhandled exception caused by passing an invalid handle to CloseHandle().

The MSDN docs for CloseHandle() state that it can raise an exception if an invalid handle is passed in.

Investigation showed that AutoIt appears to be passing an uninitialized value to CloseHandle(). If the value happens to be zero, the process doesn't crash. If the value is non-zero, the process crashes.

The exception was also reproduced on the free build of Windows when attaching a debugger to the process.

How to reproduce:

1. Run AutoIt either on the checked build of Windows or with a debugger attached
2. Run it from a command prompt without specifying a script (a script can be specified, but it is unnecessary to reproduce the exception).
3. Hit 'cancel' on the file dialog when it opens

The exception seems to be dependent on the process environment. Running the executable from different directories or with different command lines can make it either occur or not occur.

This was seen with both version 3.3.8.0 and 3.3.9.1