FileDialog browse button: how do you specify the default directory

[Amy Blankenship]

Aw, mannnnn....

;-)

 

[Stephen Lebans]

It's not like you did not deserve it Amy. In the 6 years I have known Allen
on these NG's I cannot remember him ever publicly Plonking anyone. He is
simply too nice a person.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.

 

[Amy Blankenship]

I'm not sure why Plonking would be considered nice or not nice. It's
certainly rather silly. And a very odd debating tactic, if you ask me.

But whatever ;-)

 

[Marshall Barton]

I don't see where a debate was taking place. Allen
explained that he had worked with the object extensively and
that it just plain doesn't work.

You stated "Haven't tried it" and then dismissed his
explanation with an off hand "So just use 2. Duh..."

The only other response that Allen could have given was
something to the effect of - So you make it work and show
everyone else how it's done. Since you felt it was
unnecessary to actually test your "solution", I think it's
fair for Allen to assume any further discussion would be a
waste of time.

 

[Amy Blankenship]

<Sigh> I asked if the dialogue opened in Save As and stated that *if it
did* then I'd expect to simply act like a dialogue and that you'd be able to
retrieve the user's selection from it and use it to do your own Save As.

Without addressing my original *if*, he asked me to theorize as to how I'd
solve the problem. If he had addressed the if, I'd have proposed a
different possible solution, but he didn't. So, then he posted a KB article
that, if you read it, states there is a problem with the *constant*, not
with the *value* of the constant. If the constant does not work and a
problem with the *value* of the constant is not mentioned, a reasonable
person might perhaps come up with the idea that the value might safely be
substituted for the constant, especially when problems with FileDialog are
often because the constants are not being interpreted properly.

If I needed to create code to do this, of course I'd test it before using
it, and if the poster's question had involved using Save As, I'd test code
before posting, but since I was merely asked to theorize and, strange as it
might seem, I do have other things to do sometimes than write code just to
test a theory.

I'm not sure where I saw that Allen stated he worked with the object
extensively and it doesn't work. Would you care to quote that for me, since
we're all insisting on extensive research before anyone posts anything here?

Hope this clarifies;

Amy

I don't see where a debate was taking place. Allen
explained that he had worked with the object extensively and
that it just plain doesn't work.

You stated "Haven't tried it" and then dismissed his
explanation with an off hand "So just use 2. Duh..."

The only other response that Allen could have given was
something to the effect of - So you make it work and show
everyone else how it's done. Since you felt it was
unnecessary to actually test your "solution", I think it's
fair for Allen to assume any further discussion would be a
waste of time.
--
Marsh
MVP [MS Access]

I'm not sure why Plonking would be considered nice or not nice. It's
certainly rather silly. And a very odd debating tactic, if you ask me.

But whatever ;-)

 

[Marshall Barton]

There was nothing theoretical about the discussion. It was
statements of fact backed up by the KB article, which
clearly states that the SaveAs functionality does not work
in Access.

I'm not sure what IF you are referring to here, but it's
clear that Allen asked IF you could explain how to use the
SaveAs option, to which you did not bother to reply.

I don't see where expressing my view of how this thread has
degraded is helping anythig so I'll give you the last word.