the mistakes in the existing fas file

[mruPRQUJ]

Hi there,

One fas file is used to check the title block of attached DWG file. It created a report. It can create a report now, but it created an additional unnecessary report as well.  Please see attached files and the image below for your reference, thank you very much in advance. 🙂

[Ed__Jobe]

First of all, an FAS file is a lisp file. You posted in the wrong forum. Secondly, an FAS file is compiled. You can't edit it or even view its contents. You have to contact the author to get any problems fixed. Third, if you can't attach a file, zip it, then post the zip file.

[mruPRQUJ]

Thank you very much for your great support! 🙂

[ec-cad]

As mentioned, the .fas file is a compiled version of the .lsp (source file). If the author has not

shared a copy of the .lsp, then your only recourse is to contact that person, and either have them

supply the source file, or fix the .fas file.

Barring that,

If you describe what the report contents are, Header, data lines, we can probably generate a new

.lsp file that you can use instead of the 'broken' .fas file. I tried loading that, and it yields errors.

It's pretty easy to batch a Lisp, and have it run on many drawings, appending to a 'report.csv' file

in current folder. From there, it's a click away from Excel.

ECCAD

[Sea-Haven]

The image is very clear can not find a file %251.xlsx is that correct name unusual to have a % in name. So where was the file normally located ? Like others need source code to look at. 

[pendean]

Is your EXCEL file really named %251 ?

Your FAS seems to be looking for support file(s) too (probably to stop any user from sharing it), which you did not share

Command: BCH_H_REPORTING
; error: bad argument type: lselsetp nil

[LDShaw]

Unless I trust the source of the FAS file I won't even download it. It's just not worth the risk of running. 

vl-registry-delete
Deletes the specified key from the Windows Registry

Oops!

[mruPRQUJ]

Thank you very much all of you. I sent an email to the author, thanks again. 🙂