> Someone must know this.
> Are shell variables all temporary to the session?
I assume you mean WSH variables when you say shell variables...
As with most programming environments, variables are stored in memory that
is allocated on a per-instance basis to the running program. When the
program is not running, it has no memory allocated, hence its variable no
> Is that why it's called shell scripting and you should use Wsh scripts
> if you want to update and store a user variable?
Shell scripting or WSH (Windows Script Host) scripting? Not sure of your
> I have a backup log file that increases by one every day.
> The x won't keep it's new value in shell scripting everything seems to
> be temporary to the session. Interactive and script mode react the
> same way, in that in a new session the variable updates are lost.
Temporary to the session, or no more permanent than the session, take your
pick. If you want certain values to survive between sessions, you have to
put them somewhere where they will be able to persist. This is often done
using files (text, ini, spreadsheets, databases, etc), or the registry.
This may seem a limitation, however I cannot imagine how difficult debugging
would be if variables were as persistent as you seem to want them to be :-)
> Sent via Deja.com http://www.deja.com/
> Before you buy.