Stack allready in memory

[oldummy]

I'm having an issue when going from one stack to another. I am getting the message that the 2nd stack is all ready in memory. I have closed and removed from memory with both stacks, restarted and had the same problem. Is there a way to get rid of this or do I just start all over? They are 2 separate stacks, none being a substack.

[SparkOut]

Make sure you have given each stack an individual name (not just the filename on disk, ie don't leave the default name in the Property Inspector)

[dunbarx]

Hi.

Are saying that in a new session, starting with a certain stack, you get this message by simply opening this other stack?

Craig

[dunbarx]

@Sparkout

Likely the names of these two stacks are not both "untitled 1" or something similar.

@oldDummy. But he makes a point, I assume that each stack is uniquely named?

Craig

[dunbarx]

Sparkout.

Just thinking here. He mentioned that the two stacks are just stacks, that is, neither is a subStack. That means that, assuming they are both saved, they must reside in two separate stackFiles.

Craig

[oldummy]

I'm not sure how to name a stack other thank in the stack inspector. They are name "Thekey" and "hold2". And yes, I get the message when I go from the sirs to the second stack. I have ran into this before and never found out why it happens.
My little project is just now complete and working well. I really am just to trying to head this off in the future.
Thanks for any alms.

[oldummy]

I have been too absorbed in this little project. I didn't mention that one of my first obstacles was not being able to set the stack password to encrypt it.
My workaround (if you want to call it that) was to dig out an old Rev Studio 4.0 installer I still have, so I could encrypt it.
I've been too absorbed in it and I did not think to mention that. I am sorry to have bothered anyone. I only just thought about it.

[dunbarx]

Hi.

The inspector is the most common place to do things like naming a stack. You can do it in other ways as well, from the message box or from any script for example.

Craig

[Klaus]

... I didn't mention that one of my first obstacles was not being able to set the stack password to encrypt it...

Is your LC dictionary broken?
It leaves no doubt about how to use and set a password, and it is, no surprise, as simple as:

Code: Select all

...
set the password of stack "your stack here" to "iwillookintothedcitionarymoreoften,promised!"
...

[richmond62]

What does 'Indy' mean?
-

[Klaus]

That was one of the license models for LC before the new pricing.
Community - Indy - Business

[richmond62]

Really? No? Surely not?

I thought it meant that the Dictionary had not been updated for a long time.

[Klaus]

Really!

Your screenshot is from the community edition, right?
That would explain it.

[richmond62]

OK, Klaus, you got me: this time.

[jacque]

Just curious, what was the name of the duplicate stack in the error dialog?