Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 236
  • Last Modified:

Saving State

In VB, how do do I save the state of a form?  For example, I have several forms that a user can progress through.  The problem I am having is when the user clicks 'Cancel' on a particular screen.  When this happens I want to redisplay the previous screen with all the same settings the user selected.  Currently, I am using the registry to keep track of state information.  Is this the best way?  What are my options?  Some example code or internet documentation would be very helpful.  Thanks.
0
hotwheels
Asked:
hotwheels
  • 3
  • 2
  • 2
  • +3
1 Solution
 
telebasicsCommented:
The registry is NOT the place to keep track of selected values, use variables, Whe are talking VB right not ASP webpages? If VB it is, you can easely collect the selected info in global variables of your main form.

An other option is to make all form layouts in the same form and then hide/display the right layout while progressing, this way you only have to collect the info at the end, and all settings are maintained until the user closes the form or clicks the final finish button.

This sollution, is more design intensive but much neater then yours, and it is how setup forms (tab forms) work
0
 
rkot2000Commented:
can you use form.visible = false to hide previous screens?
and form.visible = true to show
0
 
DiveblueCommented:
rkot2000 has the better answer here. Global variales are generally discouraged if you can use a lesser scope to do the job (ie form or procedure level variables) Simply hiding a form will retain all listbox selections, textbox valus, etc. They'll still be there when you show the form again. If you're holding info in form level variables, be aware of this:

If you use syntax like
form1.Show
'set some form level vars
''''more stuff
unload form1

when you do a form1.show again, he form level vars will still hold the vals you set before you unloaded (sounds like you may want to use this to your advantage)


in contrast, the following will not retain values from myform.show to the next.


Dim myForm as form1
Set myForm = new Form1
myForm.Show

'set vals
unload myform

Set myForm = new Form1
myForm.Show
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
amit_panjwaniCommented:
hotwheels,

Firstly , Storing settings in registry may be right choice if no of settings is limited.

By the way - do you want values to persist even when user has closed application ?

or Is it that you just want to maintain state for current session ?

Amit
0
 
Ryan ChongCommented:
Hi hotwheels,

Depends on what you need in your application.

Keeping the values in registry is a choice, alternatively you can also store the values in a INI file, or use a normal file that you can define the method to read/ write from it.

Using registry is good as its location never changed.

regards.
0
 
telebasicsCommented:
Use the registry only for settings you want to maintain even after software is close, pc is rebootde, etc. but for a current sellection, and therefor var's wich are only used temperorly and is not the right way to go.

I agree with rkot2000 as it is like i stated as seconde and more preferable sollution in my first post, hiding/showing layouts is better.
0
 
Ryan ChongCommented:
> hiding/showing layouts is better
Only when few forms are loaded or in a small application bcos memory will be loaded as forms are loaded..
0
 
telebasicsCommented:
well, these are the sollutions, looks like it is a personal choice what is better, i personaly try to keep the registry as clean as i can.

btw, you can use multiple "forms" in one form object, like using the tab control, on form holds many, wich all get hidden and only the one you want to show gets shown, one piece of memory, and when your totaly done unload the form and memory is free, dont forget to save ;-)
0
 
hotwheelsAuthor Commented:
All of these suggestions are great!  I am real busy right now, and it will take me some time to test out the solutions.  I only need the variables during the current session.  However, the memory use is a large factor.  Thank you all very much for your comments.  I will assign points within two weeks.
0
 
amit_panjwaniCommented:
Hotwheels

If you need to save state for current session,then you might like to add properties to FORM, similar to classes Let/Get


Hope this Helps
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now