Creating a wizard!

  • Thread starter Thread starter Niklas Östergren
  • Start date Start date
N

Niklas Östergren

Hi!

I´m creating a wizard in my app. but havné put much thought about how this
should work until now when I´m actually facing it.

So far I have created 5 fom´s that will be opened one after the other and at
the same time the second form is opened I close the first form, and so on
for all form´s. ´The user have 2 options after filling each form with data
<cmdAbort> and <cmdNext>. Where <cmdAbort> ask the user if the data entered
in the form shall be delted and after the selection from the user closes the
form. This goes in all my form´s so far. And if user select <cmdNext> the
next form openes and the current form closes.

I don´t think this is a good approach and would like to heare how do you
solve this? I´m thinking of if the user select´s <cmdAbort>. Isn´t it farley
common that the user step´s back to the form before (ex. if the user select
<cmdAbort> in form 4, form 4 closes and form 3 opens with the same data that
the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it possibel to set
it´s property [Visible] = False and switch it back to [Visible] = True when
needed?

TIA!
// Niklas
 
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.
 
Hi Nick!

Ok! Thank´s for clearing things out a little for me. I´ll take a closer look
at it and I´m NOT sattisfyed with what I have today so I´ll reedo it, which
I hate :-).

Thanks for a quick reply!

// Niklas


Nick Coe (UK) said:
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.

SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
 
Hi Niklas,

There is a "Wizard Building Wizard" that helps you through this whole process.
Just like Nick mentioned they use the standard Back, Next, Finish and Cancel buttons.
What it does is use one main form with one subform container.
Pressing the various buttons swaps in a new subform into the container. Works very nice.

Now for the bad news. I believe Microsoft only has this Add-In available for Access 97.
I have not been able to find a later version, but one may exist.
Here is the 97 version:

ACC97: Wizard Building Wizard Available in Download Center
http://support.microsoft.com/default.aspx?scid=kb;en-us;172184

--
Jeff Conrad
Access Junkie
Bend, Oregon

Niklas Östergren said:
Hi Nick!

Ok! Thank´s for clearing things out a little for me. I´ll take a closer look
at it and I´m NOT sattisfyed with what I have today so I´ll reedo it, which
I hate :-).

Thanks for a quick reply!

// Niklas


Nick Coe (UK) said:
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.

SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
Click to expand...
 
OK!

Thank´s I´ll take a look at this one. Right now I´m using A2002.

// Niklas


Jeff Conrad said:
Hi Niklas,

There is a "Wizard Building Wizard" that helps you through this whole process.
Just like Nick mentioned they use the standard Back, Next, Finish and Cancel buttons.
What it does is use one main form with one subform container.
Pressing the various buttons swaps in a new subform into the container. Works very nice.

Now for the bad news. I believe Microsoft only has this Add-In available for Access 97.
I have not been able to find a later version, but one may exist.
Here is the 97 version:

ACC97: Wizard Building Wizard Available in Download Center
http://support.microsoft.com/default.aspx?scid=kb;en-us;172184

--
Jeff Conrad
Access Junkie
Bend, Oregon

Niklas Östergren said:
Hi Nick!

Ok! Thank´s for clearing things out a little for me. I´ll take a closer look
at it and I´m NOT sattisfyed with what I have today so I´ll reedo it, which
I hate :-).

Thanks for a quick reply!

// Niklas


"Nick Coe (UK)" <[email protected]> skrev i meddelandet
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----

Niklas Östergren wrote:
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.


SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
Click to expand...
 
Hi,

You could consider buying Access 2002 Desktop Developers Handbook by Kitwin,
Getz & Gunderloy as there is a Wizard example included with the sample code
and the book talks through how to do it.

It enabled me to create a couple of wizards with relative ease.

See http://www.developershandbook.com/

--
HTH

Mark Phillipson

Free Add-Ins at; http://mphillipson.users.btopenworld.com/
Niklas Östergren said:
OK!

Thank´s I´ll take a look at this one. Right now I´m using A2002.

// Niklas


Jeff Conrad said:
Hi Niklas,

There is a "Wizard Building Wizard" that helps you through this whole process.
Just like Nick mentioned they use the standard Back, Next, Finish and Cancel buttons.
What it does is use one main form with one subform container.
Pressing the various buttons swaps in a new subform into the container. Works very nice.

Now for the bad news. I believe Microsoft only has this Add-In available for Access 97.
I have not been able to find a later version, but one may exist.
Here is the 97 version:

ACC97: Wizard Building Wizard Available in Download Center
http://support.microsoft.com/default.aspx?scid=kb;en-us;172184

--
Jeff Conrad
Access Junkie
Bend, Oregon

Niklas Östergren said:
Hi Nick!

Ok! Thank´s for clearing things out a little for me. I´ll take a closer look
at it and I´m NOT sattisfyed with what I have today so I´ll reedo it, which
I hate :-).

Thanks for a quick reply!

// Niklas


"Nick Coe (UK)" <[email protected]> skrev i meddelandet
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----

Niklas Östergren wrote:
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.


SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
Click to expand...
 
Hi Mark!

Ok, that sound´s like a good idéa. I just can´t figure out which volume you
are refering to?

// Niklas


Mark Phillipson said:
Hi,

You could consider buying Access 2002 Desktop Developers Handbook by Kitwin,
Getz & Gunderloy as there is a Wizard example included with the sample code
and the book talks through how to do it.

It enabled me to create a couple of wizards with relative ease.

See http://www.developershandbook.com/

--
HTH

Mark Phillipson

Free Add-Ins at; http://mphillipson.users.btopenworld.com/
Niklas Östergren said:
OK!

Thank´s I´ll take a look at this one. Right now I´m using A2002.

// Niklas


Jeff Conrad said:
Hi Niklas,

There is a "Wizard Building Wizard" that helps you through this whole process.
Just like Nick mentioned they use the standard Back, Next, Finish and Cancel buttons.
What it does is use one main form with one subform container.
Pressing the various buttons swaps in a new subform into the container. Works very nice.

Now for the bad news. I believe Microsoft only has this Add-In
Click to expand...
available
for Access 97.
I have not been able to find a later version, but one may exist.
Here is the 97 version:

ACC97: Wizard Building Wizard Available in Download Center
http://support.microsoft.com/default.aspx?scid=kb;en-us;172184

--
Jeff Conrad
Access Junkie
Bend, Oregon

Hi Nick!

Ok! Thank´s for clearing things out a little for me. I´ll take a
Click to expand...
closer
look
at it and I´m NOT sattisfyed with what I have today so I´ll reedo it, which
I hate :-).

Thanks for a quick reply!

// Niklas


"Nick Coe (UK)" <[email protected]> skrev i meddelandet
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----

Niklas Östergren wrote:
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.


SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
Click to expand...
 
One way to avoid the messiness of making groups of controls visible and
invisible is to use a tab control.
You can set its style to NoTabs, so users can't tab through out of order
(unless you want to let them - in which case choose a different style.)

Then instead of opening/closing (showing/hiding) forms, you can change the
value of the tab control.

Nick Coe (UK) said:
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.

SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
 
OK, another way of doing the same thing!

Since I havn´t done this before I don´t know which one to use. So I´ll try
one of them and see what I think of it.

Thanks for sharing your knowledge with me.

// Niklas

MacDermott said:
One way to avoid the messiness of making groups of controls visible and
invisible is to use a tab control.
You can set its style to NoTabs, so users can't tab through out of order
(unless you want to let them - in which case choose a different style.)

Then instead of opening/closing (showing/hiding) forms, you can change the
value of the tab control.

Nick Coe (UK) said:
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.

SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
Click to expand...
 
MacDermott said:
One way to avoid the messiness of making groups of
controls visible
and invisible is to use a tab control.
You can set its style to NoTabs, so users can't tab
through out of
order (unless you want to let them - in which case choose
a different
style.)

Then instead of opening/closing (showing/hiding) forms,
you can
change the value of the tab control.
Click to expand...

Hi Mac,

I avoided the Tab suggestion because of this label flicker
nonsense in A2003 Tabs with XP, thought it would just
complicate matters initially.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----
 
It is the Desktop edition Chapter 18.

http://www.developershandbook.com/4009Outline.asp

--
HTH

Mark
Niklas Östrergren said:
Hi Mark!

Ok, that sound´s like a good idéa. I just can´t figure out which volume
you
are refering to?

// Niklas


Mark Phillipson said:
Hi,

You could consider buying Access 2002 Desktop Developers Handbook by Kitwin,
Getz & Gunderloy as there is a Wizard example included with the sample code
and the book talks through how to do it.

It enabled me to create a couple of wizards with relative ease.

See http://www.developershandbook.com/

--
HTH

Mark Phillipson

Free Add-Ins at; http://mphillipson.users.btopenworld.com/
Niklas Östergren said:
OK!

Thank´s I´ll take a look at this one. Right now I´m using A2002.

// Niklas


"Jeff Conrad" <[email protected]> skrev i meddelandet
Hi Niklas,

There is a "Wizard Building Wizard" that helps you through this whole
process.
Just like Nick mentioned they use the standard Back, Next, Finish and
Cancel buttons.
What it does is use one main form with one subform container.
Pressing the various buttons swaps in a new subform into the
container.
Works very nice.

Now for the bad news. I believe Microsoft only has this Add-In available
for Access 97.
I have not been able to find a later version, but one may exist.
Here is the 97 version:

ACC97: Wizard Building Wizard Available in Download Center
http://support.microsoft.com/default.aspx?scid=kb;en-us;172184

--
Jeff Conrad
Access Junkie
Bend, Oregon

Hi Nick!

Ok! Thank´s for clearing things out a little for me. I´ll take a closer
look
at it and I´m NOT sattisfyed with what I have today so I´ll reedo
it,
which
I hate :-).

Thanks for a quick reply!

// Niklas


"Nick Coe (UK)" <[email protected]> skrev i
meddelandet
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----

Niklas Östergren wrote:
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.


SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
Click to expand...
 
Thanks!

// Niklas


Mark Phillipson said:
It is the Desktop edition Chapter 18.

http://www.developershandbook.com/4009Outline.asp

--
HTH

Mark
Niklas Östrergren said:
Hi Mark!

Ok, that sound´s like a good idéa. I just can´t figure out which volume
you
are refering to?

// Niklas


Mark Phillipson said:
Hi,

You could consider buying Access 2002 Desktop Developers Handbook by Kitwin,
Getz & Gunderloy as there is a Wizard example included with the sample code
and the book talks through how to do it.

It enabled me to create a couple of wizards with relative ease.

See http://www.developershandbook.com/

--
HTH

Mark Phillipson

Free Add-Ins at; http://mphillipson.users.btopenworld.com/
OK!

Thank´s I´ll take a look at this one. Right now I´m using A2002.

// Niklas


"Jeff Conrad" <[email protected]> skrev i meddelandet
Hi Niklas,

There is a "Wizard Building Wizard" that helps you through this whole
process.
Just like Nick mentioned they use the standard Back, Next, Finish and
Cancel buttons.
What it does is use one main form with one subform container.
Pressing the various buttons swaps in a new subform into the
container.
Works very nice.

Now for the bad news. I believe Microsoft only has this Add-In available
for Access 97.
I have not been able to find a later version, but one may exist.
Here is the 97 version:

ACC97: Wizard Building Wizard Available in Download Center
http://support.microsoft.com/default.aspx?scid=kb;en-us;172184

--
Jeff Conrad
Access Junkie
Bend, Oregon

Hi Nick!

Ok! Thank´s for clearing things out a little for me. I´ll take a closer
look
at it and I´m NOT sattisfyed with what I have today so I´ll reedo
it,
which
I hate :-).

Thanks for a quick reply!

// Niklas


"Nick Coe (UK)" <[email protected]> skrev i
meddelandet
Niklas,

Yes... :-)

Actually to be serious, yes. Your assumptions are good and
logical.

This is one of those things where people vary what they do.
Personally I say stick to the way MS present their wizards
with Back, Next, Finish and Cancel buttons. Use your
cmdAbort for the Cancel and add new one for cmdBack (or
cmdPrevious if you prefer).

You can hide or preferably grey out the buttons when their
function is not permissable in the flow of the wizard.

Hiding forms is perfectly possible using .Visible = False
in fact it's the preferred way really. Open them all hidden
except the first one right at the beginning. Just remember
to explicitly Close everything when done! :-)

An alternative would be to use one form with groups of
hidden controls that you make visible as required, I don't
favour this method since it can make design view, and hence
design work, a mess.

--
Nick Coe (UK)
AccHelp v1.01 Access Application Help File Builder
http://www.alphacos.co.uk/
Download Free Copy
----

Niklas Östergren wrote:
Hi!

I´m creating a wizard in my app. but havné put much
thought about how
this should work until now when I´m actually facing it.


SNIP

I don´t think this is a good approach and would like to
heare how do
you solve this? I´m thinking of if the user select´s
<cmdAbort>.
Isn´t it farley common that the user step´s back to the
form before
(ex. if the user select <cmdAbort> in form 4, form 4
closes and form
3 opens with the same data that the user have entered)?

Now to my concrete Q:
- How do you solve this? Do you minimize the form or is it
possibel
to set it´s property [Visible] = False and switch it back
to
[Visible] = True when needed?

TIA!
// Niklas
Click to expand...
Click to expand...
Click to expand...
 
Back
Top