Modify

Opened 9 years ago

Closed 9 years ago

#1527 closed Bug (Completed)

@ScriptDir & "\Test1.xls"

Reported by: Volly Owned by: Jpm
Milestone: 3.3.7.0 Component: Standard UDFs
Version: 3.3.6.0 Severity: None
Keywords: Cc:

Description

The example script for _ExcelBookSaveAs points to @ScriptDir & "\Test1.xls". The file is missing from the examples folder. The example for _WordAttach does have the "Test.doc" file in the example folder. I know it is a simple thing to add the xls file to the folder to make it work, but would it not be better to add it to the build so that the example script can find the file?
I also know the script will work in that it will display an error saying the file can't be found. However, isn't one of the points of the example script is to show how the command in question works in action?

Attachments (0)

Change History (6)

comment:1 follow-up: Changed 9 years ago by Jpm

  • Resolution set to No Bug
  • Status changed from new to closed

_WordAttach does not have a test.doc either you can verify it is failing.
Doc example are not all free of error at execution. They just try to give representative examples ...
We don't plan to have them functional.

comment:2 in reply to: ↑ 1 Changed 9 years ago by Valik

  • Resolution No Bug deleted
  • Status changed from closed to reopened

Replying to Jpm:

We don't plan to have them functional.

Then why do we have examples? If we can't provide a working example then we shouldn't provide an example at all. Otherwise we should provide a working one. I'm reopening this.

comment:3 Changed 9 years ago by Jpm

You can open one test.doc too.
Not all the scripts have the corresponding data file just the script.
But well that another big task to have all examples working on any windows

comment:4 Changed 9 years ago by Valik

I know, heaven forbid we actually provide working examples of how to use our language, right?

comment:5 Changed 9 years ago by Jpm

  • Owner changed from Gary to Valik
  • Status changed from reopened to assigned

comment:6 Changed 9 years ago by Jpm

  • Milestone set to 3.3.7.0
  • Owner changed from Valik to Jpm
  • Resolution set to Completed
  • Status changed from assigned to closed

Added by revision [5814] in version: 3.3.7.0

Guidelines for posting comments:

  • You cannot re-open a ticket but you may still leave a comment if you have additional information to add.
  • In-depth discussions should take place on the forum.

For more information see the full version of the ticket guidelines here.

Add Comment

Modify Ticket

Action
as closed The owner will remain Jpm.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.