Confirming a Save command

[Yates, Glen]

Um, wouldn't it be easier to just check the result of your save command.

For Example:

	save stack "yourstack"
	if the result is not empty then
		#stack wasn't saved
		#put error handler here
	else
		#everything was hunky-dory
	end if

-Glen Yates

> Here is what I currently am doing.
> 
> 1.  Get a reading of the time (the seconds) and put this into 
> a field in
> the stack to be saved and also in a variable.
> 
> 2.  Perform the save command.
> 
> 3.  Close the stack, and delete it from memory.
> 
> 4.  Open the stack again.
> 
> 5.  Compare the time in the variable with what is in the field in the
> stack.  If they are the same, the save happened.  If they are 
> different, it
> did not.
> 
> For my particular situation where confirming saving is 
> crucial, the stack
> can be invisible the whole time while this closing and deleting and
> reopening is going on, so these steps will not be a distraction to the
> user. If that were not the case, this method would be unacceptable.
> 
> There ought to be a better way to do this.  Anyone?
> 
> John Kiltinen
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ++++++++++
>  John Kiltinen (kiltinen at nmu.edu)        Home              Office
>  Professor, Dept. of Math. & CS   Tel.(906) 228-8035 or (906) 227-1600
>  Northern Michigan University     Fax (906) 228-4667 or (906) 2272010
>  Marquette, MI 49855 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> ++++++++++
> 
> 
> _______________________________________________
> metacard mailing list
> metacard at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/metacard
>