Opened 18 years ago
Closed 18 years ago
#484 closed Bug (Fixed)
ObjGet failures
| Reported by: | Spiff59 | Owned by: | Valik |
|---|---|---|---|
| Milestone: | 3.2.13.7 | Component: | AutoIt |
| Version: | 3.2.12.0 | Severity: | None |
| Keywords: | Cc: |
Description
ObjGet doesn't seem to be doing what I expect it to.
I placed files named "test.doc", "test.txt" and "test.xls" in my root folder and used the following code to test:
$file = "C:\" & InputBox("","file?")
$oExcel = ObjGet($file)
If @error Then
msgbox(1,"", "Path Not Found for: " & $file)
Else
msgbox(1,"", "Path Found for: " & $file)
EndIf
Exit
ObjGet appears to be sometimes functioning like "FileExists", ruturning 0 whether the file is in use or not.
Sometimes ObjGet works the first time a file is referenced, and then continues to report it (after thinking for a few seconds) as active long after the process was closed. Oddly, when referencing a previously opened .txt file, ObjGet consistantly causes autoit3.exe to abend with 0xc0000005 at offset 00042a376. Just with the .txt extension. Weird...
The only other factors that may be in play here that I can think of are that this PC did get the recent SP3 update to XP Pro, and that I'm running my tests interpretively, via SciTE, rather than as compiled stand-alones.
Thanks.
Attachments (0)
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Milestone: | → 3.2.13.7 |
|---|---|
| Owner: | set to |
| Resolution: | → Fixed |
| Status: | new → closed |
Fixed in version: 3.2.13.7

Replying to Spiff59:
And your expectations are?
A text file does not have a COM interface. While it shouldn't crash, you won't get an object from it either.
This is a shitty bug report. You've rambled on a lot and other than a crash (when you use the function wrong, I might add) I don't really know what's happening or what you expect to happen. Tell me what you think ObjGet() does and what you are trying to achieve. Tell me what happens when you run that script with *existing* Excel and Word files.