Actually, Yes and No would be much better. Even for this it will need
checkboxes because it is done already, but for other, and it will be
more like that, thats for sure, I will use Yes, No...
Actually I never thought of that. It is much easier solution and I
can use √ in data validation. And I dont need macro for hiding all.
It is very nice and easy solution.
Thanks for that too.
The point of using the checkbox-like cells was a more efficient way to
deal with the 100s of selections possible on this questionaire! It's
much easier (and more user friendly) to double-click a checkbox cell
than click a DV down arrow, scroll the list if numerous choices, and
click their preference. Not saying this is a good thing for your
project if checkbox choices aren't suitable, though<g>.
How it handled options was...
Qs asked were dependant on earlier choices;
Options were listed in rows below the Q, and the choices were also
dependant on earlier choices relevant to the Q;
The DV dropdown was below the options rows. This list was also
dependant on the Q and its available options. So, for example, if
there were 3 options for a Q, 1 of which was disabled based on
earlier choices (say #2), then the DV list contained only 1 and 3.
Users had a choice, then, to use the DV list or enter directly
into its cell.
So, for example, if you've seen printed forms that ask a yes/no Q and
provide another field for 'If Yes then provide details...' or whatever.
Well on this form selecting Yes of double-clicking a checkbox
automajically displays (or hides) the next step.
<FWIW>
I started making forms like this in XL4.x! I started adding event code
features in XL2000. I'll be the 1st to admit it's daunting and can get
very wieldy, but you end up with some pretty pro-looking survey wizards
when it's all done.
This was also duplicated in a userform version so you could have a UI
choice of either sheet-based, form-based, or both! Either choice
displays a sheet-based 'summary' for reviewing which allowed going back
to to edit any particular section. Both also had a 'Navigator' panel
where you could 'jump' to any section. The sheet-based version uses a
DV list, the userform uses a listbox same as an options dialog would
have.
In some cases I've used a treeview when clients wanted to be able to
expand/colapse section nodes to show/hide subsections. I haven't done
this, though, since MS stopped including the "Microsoft Windows Common
Controls" in Windows starting with Vista because it meant having to
include the mscomctl.ocx with the project. The issue at the time was
that every app that uses them had to include them in their installers
or their apps wouldn't run! (Thanks MS!)
I'm back using them again having implemented a resolve conditional on
if the controls are missing on a users machine; my project registers
the controls at startup for use during runtime, then unregisters them
at shutdown. Otherwise, if another app fully installs the controls for
their use then my projects use those because they pre-exist at startup.
(This preserves my primary policy that my projects be 100% portable in
that they do not use the Registry and they cleanup after themselves at
shutdown so the host computer is not changed in any way!)
HTH...
--
Garry
Free usenet access at
http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion
