efs failing syntax check

[arieal]

Hi
46. After installing eSignal 7.9.1 a few weeks ago, today I wanted to do some coding and my old code would not compile/syntax check.

I went backward to my earliest stuff and I found this:

- Sample_TargetStop.efs - passes the syntax check.
This is code public available in esignal.

- aaMAcross_pt.efs - does not pass the syntax check even so that it is largely based on the previous code.

Do you know of anything I need to do to pass this check in 7.9.1 ?

How do I attach 2 files to this message?

Many thanks
Arie

[Guest]

Arie,

You can only attach one file per post. If you want to post more files per message you would have to upload the files to a fileshare account and post links.

[arieal]

Steve, thanks.

Here is the first file mentioned in my previous post.

This file, Sample_TargetStop.efs, does pass the syntax check.

The second file, attached in my previous post, does not pass the check.
Even more, it crashes the esignal so that I have no indication of what's wrong.

Before I begin the 'salami' method of slicing the code to find out what is wrong, I suspect that it might be some esignal stuff related to 7.9.1 that is causing this problem.

I had no problems with these files in the previous esignal load.

Arie

[Guest]

Arie,

Here is the error I get with the syntax checker with the aamacross efs.

Local Settings\Temporary Internet Files\Content.IE5\DG29ABY7\aamacross_pt[1].efs, line 129: Formula file not found: /Kwik POP/TSKPAUTOSTOP.efs

Of course I do not have Kwick POP stuff installed, but your problem may be related to that as well. What is the full path of your folder where you keep this file?

FWIW, the nature of this thread is such that you may not be getting as much help as you could from the community. Check out forum posting guideline #3. Seperate threads, with descriptive titles encourage others in the community to help out. An encyclopedic thread such as this really limits community involvement IMHO.

[arieal]

Steve

Many, many thanks for your help.

If I take out this line, it checks ok.

But, why this path:

var autostop = call("/Kwik POP/TSKPAUTOSTOP.efs");
is not recognized anymore I still do not know.

I do have the TSKPAUTOSTOP.efs under the path:
c:\program files\esignal\formulas\kwik pop\

and the file aamacross efs under
c:\program files\esignal\formulas\backtesting\

Nothing changed in my file system since I updated to 7.9.1 except creating a new directory under \backtesting\ which has no bearing on these files.

Thanks
Arie

[arieal]

Steve

Another question is how come that I crashed while syntax checking this file, and you managed to get the errors in the Formula Output?

Arie

[Guest]

Arie,

You are most welcome. Understand the reason I received this error was most likely due to me not having the kwik pop code. What error are you getting?

I am not sure why you crashed, that by itself is not a good sign. (more than likely your error is not the kwik pop error that I received). However, you can still get to the output sent to the formula output window by opening the formulaoutput.log in the eSignal directory.

You know, perhaps the error is due to the encryption of the kwik pop efs. In fact, after performing a search of the forum, that is the most likely reason. Check out this link as it discusses the issue.

[arieal]

Steve

Thanks again for your reply.

The TSKPAUTOSTOP.efs is not encoded and it is under:
c:\program files\esignal\formulas\kwik pop\

The call to this efs is:
var autostop = call("/Kwik POP/TSKPAUTOSTOP.efs");

The formulaoutput.log says:
Formula file not found:
No Syntax Errors

So, obviously esignal doesn't find this file, even though nothing relevant changed in my directories to prevent finding this file.

Did esignal change the way a called file's path is supposed to be spelled out?
Maybe not call("/.../...") but call("\...\...") or something else?

Thanks
Arie

[ACM]

Arie

Did esignal change the way a called file's path is supposed to be spelled out?
Maybe not call("/.../...") but call("\...\...") or something else?

Not that I am aware of [btw if you use a backslash in the path you need to precede it with an \ ie call("\\...\\..")].
Did you install the upgrade over the prior version? Check the Formula Root path. To do this select Tools-> EFS-> Settings from the main menu
Alex

[arieal]

Alex,
Thanks very much for your reply.

Yes, I did update esignal 7.9.1 on top of the previous version of esignal.

My settings for Formula Root are:
c:\program files\esignal\formulas

I did change the way to call this file to:
var autostop = call("C:\\Program Files\\eSignal\\Formulas\\Kwik POP\\TSKPAUTOSTOP.efs");

This time the check didn't crash my esignal but I got the error:
'Formula file not found: C:\Program Files\eSignal\Formulas\Kwik POP\TSKPAUTOSTOP.efs'

This tskpautostop.efs file calls a dll in a different directory in the right way, with double \\ etc., and nothing changed here since ages and it worked in the previous esignal version.

Why the new esignal version is making problems is a mistery.

Thanks
Arie

[ACM]

Arie
The error message suggests that the efs is not in the folder defined in the path of the call function.
If you run a Windows Search for that file what path do you get?
Alex

[arieal]

Alex

The search results:
- c:\program files\esignal\formulas\kwik pop\
- My Computer - My note: no other info available
- C:\documents and settings\Arie\Recent - size=1kb, type=shortcut, My note: not visible in windows explorer, probably it is a hidden file?

Thanks much
Arie

[ACM]

Arie
Other than something having gone wrong during installation I cannot think of a reason as to why that call would return a Formula file not found error message. You may want to try reinstalling 7.9.1 again over the existing copy and see if that fixes the problem you are having
Alex