Baksteen Posted October 7, 2011 Share Posted October 7, 2011 (edited) Ok, So I'm in the process of going through my scripts to make them work for windows 7. They have been scripted on windows XP with the latest release build of AutoIt and work fine there. On Windows 7 they did not work so I downloaded the latest version of the AutoIt beta and started debugging. One thing I'm coming across is when I run the attached code, it gives me the "test" msgbox even though I have not opened the excel file, where in XP it would've set @error. The script even reads data from the closed excel file (the consolewrite gives me the correct data). It can't write to the file however. The _Excelbookopen seems to be working allright so far. Is this supposed to be like that, am I doing something wrong? Or is it a bug? Thanks in advance for any help on this.test.au3 Edited October 7, 2011 by Baksteen Link to comment Share on other sites More sharing options...
Baksteen Posted October 11, 2011 Author Share Posted October 11, 2011 Hmm, I'm bumping this, is this known by the developers or looked into, or am I just doing something wrong here? Any feedback is much appreciated. Link to comment Share on other sites More sharing options...
bogQ Posted October 11, 2011 Share Posted October 11, 2011 (edited) well i dont know if this is important _ExcelBookAttach($s_string $s_string String to search for I c that you added location and not win name string if you in some moment closed excel with autoit and trying to retest if its open or somethimg similar, try before test to do $oExcel = "" on old object, maby ilt help maby not. Edited October 11, 2011 by bogQ TCP server and client - Learning about TCP servers and clients connectionAu3 oIrrlicht - Irrlicht projectAu3impact - Another 3D DLL game engine for autoit. (3impact 3Drad related) There are those that believe that the perfect heist lies in the preparation.Some say that it’s all in the timing, seizing the right opportunity. Others even say it’s the ability to leave no trace behind, be a ghost. Link to comment Share on other sites More sharing options...
Baksteen Posted October 19, 2011 Author Share Posted October 19, 2011 Hi, I'm bumping this one last time, hoping someone can tell me if I'm doing something wrong. I want to post this as a bug in the beta issue tracker because the problem still seems to be there in the latest beta version (3.3.7.19), but I'm not totally sure if I'm doing it wrong or... The thing is, this has always worked on XP with the latest release version. I'm hoping someone can reconstruct the issue. Link to comment Share on other sites More sharing options...
Juvigy Posted October 19, 2011 Share Posted October 19, 2011 Is it 64bit windows ? Did you check if you have excel.exe process before executing the script? Link to comment Share on other sites More sharing options...
Baksteen Posted October 20, 2011 Author Share Posted October 20, 2011 The CPU should be 64bit capable (Allthough I'm not sure, it's not my machine), but the installed windows 7 version is 32 bit. I've no running Excel processes, it also happens when I do a fresh restart. I worked around it using excelbookopen instead, which seems to work fine. If I would have running excel processes the file would probably only be allowed to open in read-only mode anyway. Thanks for any suggestions though. This probably should be looked into by the devs I guess, but I'm still a newbie so I'm not sure either. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now