• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Bug in (scripting) Excel.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in (scripting) Excel.


  • Subject: Re: Bug in (scripting) Excel.
  • From: Deivy Petrescu <email@hidden>
  • Date: Sun, 28 Sep 2003 18:31:16 -0400

On Sunday, Sep 28, 2003, at 11:35 US/Eastern, kai wrote:

While I can appreciate both points (c'mon kai, get down off the fence!), I
tend to share Deivy's view that Excel should still perform as normal - just
without updating the on-screen representation of events.


kai, thanks for your independent opinion (I'll send you the money as we've discussed earlier...)

Actually, when i noticed that the problem was screenupdate, I pondered for a while if I had jumped the gun because of the nature of the command, although I felt I did not


(Even copy and paste commands work here with screen updating off.)

The above behaviour is what I would expect - or at least hope for.

To script Excel, I generally start without considering screen updating - so
I can see what's going on. In the final stages, I then insert screen
updating off/on commands at appropriate points. If turning off screen
updating cripples certain commands, I imagine quite a few of my Excel
scripts would fall over.



I believe that this is the reason it is a bug!
Anybody familiar with this command and scripting, would first debug the script runing it with a bunch of logs and stops and checking the behavior of the interaction script-excel. If the command whose purpose is to speed up the process is going to change the original process, what is it good for? All the time checking the program is wasted.
I did waste a lot of time. The script would run flawlessly with one point only when testing and fail completely when run in batch
mode.
Another point is it replies back to a true when a window is activated. Well to be consistent with should return a false or throw an error.


The behaviour of Excel X seems, in this respect, to be inconsistent with
previous versions. Since I don't consider the change an enhancement, I'm
still tempted to conclude that it's a bug.

---
kai

Again, thanks, your points were very good.
Since I do not have SE or Smile in earlier than X versions here, could you check that this script would error in 9.2:

tell Application "Microsoft Excel"
set ScreenUpdating to false
Open "Hard Disk:Desktop Folder:Excel Tests:xlTest1"
Open "Hard Disk:Desktop Folder:Excel Tests:xlTest2"
Open "Hard Disk:Desktop Folder:Excel Tests:xlTest3"
Tell Window "xlTest1"
LastCell Range "A1" Direction xlToRight
get Column of Range "R1C4" of Worksheet "Sheet1" of Workbook "xlTest1"
end tell
end tell

It errors here.

Thanks

Deivy
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Bug in (scripting) Excel. (From: kai <email@hidden>)

  • Prev by Date: Re: Bug in (scripting) Excel.
  • Next by Date: Re: Bug in (scripting) Excel.
  • Previous by thread: Re: Bug in (scripting) Excel.
  • Next by thread: Re: Bug in (scripting) Excel.
  • Index(es):
    • Date
    • Thread