Larry Linson wrote:[color=blue]
> "Deano" wrote
>[color=green]
> > Do you want to offer them a control
> > that allows them to traverse the file
> > system? I decided against it given how
> > bad the average user is with
> > Windows.[/color]
>
> Interesting that our experience in this area should differ so vastly.
> I've never had users who had any trouble at all using the Windows
> Common Dialog, just as in any other application.[/color]
I've read one or two articles recently that have cast doubt on any notions
that Windows is actually a positive experience for the end user in terms of
it's basic functions and windowing concepts. i.e users don't really value,
for example, being able to resize and position windows. And that they don't
really find it easy to locate files and data. Heck, even I can't easily
find stuff most of the time. The interface to the filesystem is NOT
intuitive and I make this bold claim since I have had to spend many hours
talking to end users over the phone and visualise them navigating down
dead-ends. This is regardless of whether they were trying to open a file
within an app or just using Windows Explorer. A few people have been
totally amazed when I typed a URL in and a website appeared....("hmm, well
what do you think that court case was about then?").
[color=blue][color=green]
> > Also it saved me the hassle of debugging that.[/color]
>
> The code, freely downloadable, from
>
http://www.mvps.org/access/api/api0001.htm has been used sufficiently
> that we know it works. The only debugging needed would be the code
> that calls it, and it even includes an example of that. It uses the
> Windows Common Dialog API directly, so no ActiveX, etc., has to be
> distributed.[/color]
Ah, this might make me a convert. Thanks.
[color=blue]
>
>[color=green]
> > I give them a textbox and tell them to
> > type it in. I save the path in a listbox from
> > which they can subsequently select.[/color]
>
> I don't follow how this could be easier for an inexperienced user than
> selecting from the Common Dialog; in fact, it seems they'd have to be
> more knowledgeable to search for the path and file name, and more
> prone to typographical errors entering it.[/color]
That's just how it works for my app; it may indeed be better to have
something more sophisticated at other times.
