put in use of filedialog in an access xp subroutine to find a folder:
Set fd = Application.FileDialog(msoFileDialogFolderPicker)
it works fine on my development machine that has the full office
installation. however when i package it up and take it to a clean machine,
install the access runtime, and try to use the filedialog it crashes with a
runtime error on the above line. i did check that the office10\mso.dll is
on the target machine. is there something else that is needed that the
packaging wizard may have missed??

You must specifically make a reference to mso10.dll


>-----Original Message-----
>put in use of filedialog in an access xp subroutine to
find a folder:
> Set fd = Application.FileDialog
(msoFileDialogFolderPicker)
>it works fine on my development machine that has the
full office
>installation. however when i package it up and take it
to a clean machine,
>install the access runtime, and try to use the
filedialog it crashes with a
>runtime error on the above line. i did check that the
office10\mso.dll is
>on the target machine. is there something else that is
needed that the
>packaging wizard may have missed??
>
>
>
>.
>

something other than checking the reference box for "microsoft office 10.0
object library" in the project references??? it wouldn't even compile on
the development machine without that of course. with it the development
machine is fine, but the target machine crashes.

<(E-Mail Removed)> wrote in message
news:144801c4ff88$a994e880$(E-Mail Removed)...
> You must specifically make a reference to mso10.dll
>
>
> >-----Original Message-----
> >put in use of filedialog in an access xp subroutine to
> find a folder:
> > Set fd = Application.FileDialog
> (msoFileDialogFolderPicker)
> >it works fine on my development machine that has the
> full office
> >installation. however when i package it up and take it
> to a clean machine,
> >install the access runtime, and try to use the
> filedialog it crashes with a
> >runtime error on the above line. i did check that the
> office10\mso.dll is
> >on the target machine. is there something else that is
> needed that the
> >packaging wizard may have missed??
> >
> >
> >
> >.
> >

Dave

I have had a number of "interesting" experiences deploying the Access
runtime solutions. Some stuff just dosent work, some stuff works
differently, and some stuff causes Kaboom's.

If I were in your position I believe that I would give up on the Access
msoFileDialogFolderPicker and use the API directly. There is a Browse for
Folder Solution at http://www.mvps.org/access/api/api0002.htm and browse for
files solution at http://www.mvps.org/access/api/api0001.htm.

Neither of these solutions requires anything special be installed on the
client machine, as they use the windows OS directly.

Ron W


"Dave" <(E-Mail Removed)> wrote in message
news:ulmVHW7$(E-Mail Removed)...
> something other than checking the reference box for "microsoft office 10.0
> object library" in the project references??? it wouldn't even compile on
> the development machine without that of course. with it the development
> machine is fine, but the target machine crashes.
>
> <(E-Mail Removed)> wrote in message
> news:144801c4ff88$a994e880$(E-Mail Removed)...
> > You must specifically make a reference to mso10.dll
> >
> >
> > >-----Original Message-----
> > >put in use of filedialog in an access xp subroutine to
> > find a folder:
> > > Set fd = Application.FileDialog
> > (msoFileDialogFolderPicker)
> > >it works fine on my development machine that has the
> > full office
> > >installation. however when i package it up and take it
> > to a clean machine,
> > >install the access runtime, and try to use the
> > filedialog it crashes with a
> > >runtime error on the above line. i did check that the
> > office10\mso.dll is
> > >on the target machine. is there something else that is
> > needed that the
> > >packaging wizard may have missed??
> > >
> > >
> > >
> > >.
> > >
>
>
>

ah, thank you... that is really the folder dialog i wanted, but i forgot how
to get it. i'll have to file that link away somewhere 'safe'.

"Ron Weiner" <(E-Mail Removed)> wrote in message
news:emn9J67$(E-Mail Removed)...
> Dave
>
> I have had a number of "interesting" experiences deploying the Access
> runtime solutions. Some stuff just dosent work, some stuff works
> differently, and some stuff causes Kaboom's.
>
> If I were in your position I believe that I would give up on the Access
> msoFileDialogFolderPicker and use the API directly. There is a Browse for
> Folder Solution at http://www.mvps.org/access/api/api0002.htm and browse
for
> files solution at http://www.mvps.org/access/api/api0001.htm.
>
> Neither of these solutions requires anything special be installed on the
> client machine, as they use the windows OS directly.
>
> Ron W
>
>
> "Dave" <(E-Mail Removed)> wrote in message
> news:ulmVHW7$(E-Mail Removed)...
> > something other than checking the reference box for "microsoft office
10.0
> > object library" in the project references??? it wouldn't even compile
on
> > the development machine without that of course. with it the development
> > machine is fine, but the target machine crashes.
> >
> > <(E-Mail Removed)> wrote in message
> > news:144801c4ff88$a994e880$(E-Mail Removed)...
> > > You must specifically make a reference to mso10.dll
> > >
> > >
> > > >-----Original Message-----
> > > >put in use of filedialog in an access xp subroutine to
> > > find a folder:
> > > > Set fd = Application.FileDialog
> > > (msoFileDialogFolderPicker)
> > > >it works fine on my development machine that has the
> > > full office
> > > >installation. however when i package it up and take it
> > > to a clean machine,
> > > >install the access runtime, and try to use the
> > > filedialog it crashes with a
> > > >runtime error on the above line. i did check that the
> > > office10\mso.dll is
> > > >on the target machine. is there something else that is
> > > needed that the
> > > >packaging wizard may have missed??
> > > >
> > > >
> > > >
> > > >.
> > > >
> >
> >
> >
>
>