Dialogs(wdDialogFileOpen) --> can't multi-select

[RJ Lohan]

There is a knowledge base article;
http://support.microsoft.com/default.aspx?scid=kb;en-
us;146922

Which outlines an issue with VBA in Word where using
Dialogs(wdDialogFileOpen) caused runtime error when
selecting multiple files. However, this article only
refers to Word 97, and I'm sure this is still an issue in
Word 2000/XP/2003

Can anyone point me to a reference to this effect?

(I know I can use Application.FileDialog for XP/2003, but
as this isn't available in Word 2000, I need to find a
reference to this issue for customer explanation)
..

 

[Jonathan West]

Take a look here

Can't open multiple files using FileOpen
http://word.mvps.org/FAQs/MacrosVBA/OpenMultipleFiles.htm

 

[RJ Lohan]

Ah, nice one. Thanks for that.

Cheers,
Ryan

Take a look here

Can't open multiple files using FileOpen
http://word.mvps.org/FAQs/MacrosVBA/OpenMultipleFiles.htm

--
Regards
Jonathan West - Word MVP
www.intelligentdocuments.co.uk
Please reply to the newsgroup

 

[RJ Lohan]

Ah, I've just discovered that that resolution probably won't do -> reason
being that I modify the action of the 'Open' button (and menu items). Which
is why I need to duplicate the open dialog in the first place...

Any other suggestions or KB links?

 

[Jonathan West]

Ah, I've just discovered that that resolution probably won't do -> reason
being that I modify the action of the 'Open' button (and menu items).
Which
is why I need to duplicate the open dialog in the first place...

Any other suggestions or KB links?

The following article has some VB code for using the Windows common dialog
for file open.

http://vbnet.mvps.org/code/comdlg/fileopendlg.htm

The code is in VB6 rather than VBA, and so you will need to adapt it a bit,
but the Windows common dialog does allow you to do multisepect.

 

[RJ Lohan]

That's probably a bit heavy for what I want - and adds a dependancy to
distribute doesn't it?

Anyway, bit of lateral thinking and I've resolved this one - I now add an
'Open' button to the toolbar and execute that one, which hasn't been hooked
by my other code. Then I delete it, and the user is none the wiser.

Thanks for the help.

Cheers,
Ryan

 

[Jonathan West]

That's probably a bit heavy for what I want - and adds a dependancy to
distribute doesn't it?

The coding it a bit inticate, but it adds no dependencies and nohing
dditional that you need distribute.

Anyway, bit of lateral thinking and I've resolved this one - I now add an
'Open' button to the toolbar and execute that one, which hasn't been
hooked
by my other code. Then I delete it, and the user is none the wiser.

Thanks for the help.

You're welcome!