Moving LS code in .lss from 8.0 to 8.5.1. Broken?

HCL Domino Domino Forum
1

I am tearing out what little hair I have left. I have a lss library that compiles perfectly well in Notes 8.0.2

I need to compile this library in DDE 851. If I transfer the code directly into a library, then DDE compiles it without error, but I must get it into an .lss file (for security). But the compiler now throws up an error on the “Use .lss” line. There’s no indication of where the problem is. By stepping line-by-line through the code and pasting it into the lss I have pinned it down to this line …

Set inputStream = session.CreateStream

Is this a bug in 851? In Vista? Can anyone help me please!!

2

Subject: RE: moving LS code in .lss from 8.0 to 8.5.1. Broken?

Have you got OPtion Declare or similar set,

Check the spellings of the declarations and variable use.

8.5 just may have something enabled by default check the Options area of the code.

3

Subject: thanks, Options does seem to be a problem

but I find that Option Declare is flagged as an error, while Option Explicit flags the .lss as the error. Either way, the script won’t compile when the code is in .lss, but it does compile when the code is direct.

Any other ideas

4

Subject: Some suggestions

Here is some suggestions (Apologies if you have already tried).

  1. The LSS file is normally used to store classes/constants for the design element. It is not used to store methods that would be executed within the design element.

So for example “Sub Initialize” will not work if it is contained in the LSS file.

  1. You have “.lss”? I take it there is an actual file name involved of the lss file? Like:

use “test.lss”

Never tried it as a file called “.lss” but probably not good coding practise.

  1. How are you storing the LSS file? As a resource in the database? Or as a file on the system? If it is as a resource, make sure the name/alias matches up with what is in the code. If it is on the system then it may be a case of visibility for the agent. Might require a higher security setting.

  2. You mentioned the code works if you fully paste it into the agent. What you can try doing is taking logical sections of the code bit by bit and move it to the LSS file and see at what point it stops working. Will help to narrow down the issue.