Rather than post all code - this error can be replicated
as follows.

(1) With a new workbook create a Form with one command
button on it.

(2) In the click event of the command button insert the
code:

Private Sub CommandButton1_Click()

Me.PrintForm
Application.Dialogs(xlDialogSendMail).Show
Unload Me

End Sub

(3) Create a module with code showing the form

(4) Add a form button to your worksheet and associate it
with the macro calling the form

(5) Let it run and - hey presto! You should get
the "Path/File Access Error" code.

Got any ideas?

Gavin






Show us your code Gavin

--
Regards Ron de Bruin
(Win XP Pro SP-1 XL2002 SP-2)
www.rondebruin.nl



"Gavin Smith" wrote
in message ...
I am experiencing a similar problem with the use of the
xlDialogSendMail object. I have a form that generates a
spreadsheet then presents the user with the dialog box,
the user enters the custom details and send the email.



This all works fine, I then unload the form, and this is
where it gets confusing. If we are in break mode and
stepping through when we reach the last 'End Sub' or
an 'End', i.e. the code is to stop running, we
get 'File/Path Not Found' error and can no loner run any
code that references any form in this workbook, or view
any form or the code behind any form in this book and get
the error message again. Other books are fine.



If we have called the book from a button, then the
procedure will run without error, but if we then try to
run any code that relates to the forms in this book we
have the difficulties as above.



I do not know if this is related but in the references
window the 'Microsoft Forms 2.0 Object Library' moves a
few slots down the list.



That’s as many clues as we can give, we are not
officially
clueless, anyone out there help?

Hi Gavin

I tested it in Win XP Office 2002 and WinXP Office 97.
No errors for me?

Do you have more information to reproduce


--
Regards Ron de Bruin
(Win XP Pro SP-1 XL2002 SP-2)
www.rondebruin.nl



"Gavin Smith" wrote in message ...
Rather than post all code - this error can be replicated
as follows.

(1) With a new workbook create a Form with one command
button on it.

(2) In the click event of the command button insert the
code:

Private Sub CommandButton1_Click()

Me.PrintForm
Application.Dialogs(xlDialogSendMail).Show
Unload Me

End Sub

(3) Create a module with code showing the form

(4) Add a form button to your worksheet and associate it
with the macro calling the form

(5) Let it run and - hey presto! You should get
the "Path/File Access Error" code.

Got any ideas?

Gavin






Show us your code Gavin

--
Regards Ron de Bruin
(Win XP Pro SP-1 XL2002 SP-2)
www.rondebruin.nl



"Gavin Smith" wrote
in message ...
I am experiencing a similar problem with the use of the
xlDialogSendMail object. I have a form that generates a
spreadsheet then presents the user with the dialog box,
the user enters the custom details and send the email.



This all works fine, I then unload the form, and this is
where it gets confusing. If we are in break mode and
stepping through when we reach the last 'End Sub' or
an 'End', i.e. the code is to stop running, we
get 'File/Path Not Found' error and can no loner run any
code that references any form in this workbook, or view
any form or the code behind any form in this book and get
the error message again. Other books are fine.



If we have called the book from a button, then the
procedure will run without error, but if we then try to
run any code that relates to the forms in this book we
have the difficulties as above.



I do not know if this is related but in the references
window the 'Microsoft Forms 2.0 Object Library' moves a
few slots down the list.



That’s as many clues as we can give, we are not
officially
clueless, anyone out there help?

Only that error occurs in Excel 2000 but not on Excel 97


-----Original Message-----
Hi Gavin

I tested it in Win XP Office 2002 and WinXP Office 97.
No errors for me?

Do you have more information to reproduce


--
Regards Ron de Bruin
(Win XP Pro SP-1 XL2002 SP-2)
www.rondebruin.nl



"Gavin Smith" wrote
in message ...
Rather than post all code - this error can be replicated
as follows.

(1) With a new workbook create a Form with one command
button on it.

(2) In the click event of the command button insert the
code:

Private Sub CommandButton1_Click()

Me.PrintForm
Application.Dialogs(xlDialogSendMail).Show
Unload Me

End Sub

(3) Create a module with code showing the form

(4) Add a form button to your worksheet and associate it
with the macro calling the form

(5) Let it run and - hey presto! You should get
the "Path/File Access Error" code.

Got any ideas?

Gavin






Show us your code Gavin

--
Regards Ron de Bruin
(Win XP Pro SP-1 XL2002 SP-2)
www.rondebruin.nl



"Gavin Smith"
wrote
in message news:081501c39e3f$60a721c0
...
I am experiencing a similar problem with the use of
the
xlDialogSendMail object. I have a form that generates
a
spreadsheet then presents the user with the dialog
box,
the user enters the custom details and send the email.



This all works fine, I then unload the form, and this
is
where it gets confusing. If we are in break mode and
stepping through when we reach the last 'End Sub' or
an 'End', i.e. the code is to stop running, we
get 'File/Path Not Found' error and can no loner run
any
code that references any form in this workbook, or
view
any form or the code behind any form in this book and
get
the error message again. Other books are fine.



If we have called the book from a button, then the
procedure will run without error, but if we then try
to
run any code that relates to the forms in this book we
have the difficulties as above.



I do not know if this is related but in the references
window the 'Microsoft Forms 2.0 Object Library' moves
a
few slots down the list.



That’s as many clues as we can give, we are not
officially
clueless, anyone out there help?




.

Hi Gavin

Same for me in 2000, but I have no solution for you.

I hope anybody else can help you



--
Regards Ron de Bruin
(Win XP Pro SP-1 XL2002 SP-2)
www.rondebruin.nl



wrote in message ...
Only that error occurs in Excel 2000 but not on Excel 97


-----Original Message-----
Hi Gavin

I tested it in Win XP Office 2002 and WinXP Office 97.
No errors for me?

Do you have more information to reproduce


--
Regards Ron de Bruin
(Win XP Pro SP-1 XL2002 SP-2)
www.rondebruin.nl



"Gavin Smith" wrote
in message ...
Rather than post all code - this error can be replicated
as follows.

(1) With a new workbook create a Form with one command
button on it.

(2) In the click event of the command button insert the
code:

Private Sub CommandButton1_Click()

Me.PrintForm
Application.Dialogs(xlDialogSendMail).Show
Unload Me

End Sub

(3) Create a module with code showing the form

(4) Add a form button to your worksheet and associate it
with the macro calling the form

(5) Let it run and - hey presto! You should get
the "Path/File Access Error" code.

Got any ideas?

Gavin






Show us your code Gavin

--
Regards Ron de Bruin
(Win XP Pro SP-1 XL2002 SP-2)
www.rondebruin.nl



"Gavin Smith"
wrote
in message news:081501c39e3f$60a721c0
...
I am experiencing a similar problem with the use of
the
xlDialogSendMail object. I have a form that generates
a
spreadsheet then presents the user with the dialog
box,
the user enters the custom details and send the email.



This all works fine, I then unload the form, and this
is
where it gets confusing. If we are in break mode and
stepping through when we reach the last 'End Sub' or
an 'End', i.e. the code is to stop running, we
get 'File/Path Not Found' error and can no loner run
any
code that references any form in this workbook, or
view
any form or the code behind any form in this book and
get
the error message again. Other books are fine.



If we have called the book from a button, then the
procedure will run without error, but if we then try
to
run any code that relates to the forms in this book we
have the difficulties as above.



I do not know if this is related but in the references
window the 'Microsoft Forms 2.0 Object Library' moves
a
few slots down the list.



That’s as many clues as we can give, we are not
officially
clueless, anyone out there help?




.