deedub84
asked on
MDE Outputto error
Hi Experts,
I have created an MDE from a FE/BE split database.
On a form, I have an option to save a report (in smp format), email it, and preview/print it. If the user initiates the save process (which opens up a standard save dialog box and then escapes out (or x's out), the attached error message is displayed.
Is there a way to avoid this error message (which I think would be confusing and counterintuitive to the user?
Thx,
Deedub84
Error.bmp
I have created an MDE from a FE/BE split database.
On a form, I have an option to save a report (in smp format), email it, and preview/print it. If the user initiates the save process (which opens up a standard save dialog box and then escapes out (or x's out), the attached error message is displayed.
Is there a way to avoid this error message (which I think would be confusing and counterintuitive to the user?
Thx,
Deedub84
Error.bmp
ASKER
Thks Cap, I have the mdb, so that's not a problem, I guess my question really is what is that error trapping, I'm not clear.
My code is bare, bare bones; see below.
Any suggestions would be great!
My code is bare, bare bones; see below.
Any suggestions would be great!
Private Sub btnPrintReport_Click()
DoCmd.OutputTo acOutputReport, "rptSummary", acFormatSNP
End Sub
( If the user initiates the save process ) where is this done?
ASKER
On a button on a form; the code for which is attached above.
In the mdb, when I cancel out of the save, I get an error 2501 "Output to action canceled".
I added "On error resume next" in the PrintReport_Click procedure; in the MDB it avoided the error message.
In the MDE though, it produced a fatal error!!
Fatal-error.bmp
In the mdb, when I cancel out of the save, I get an error 2501 "Output to action canceled".
I added "On error resume next" in the PrintReport_Click procedure; in the MDB it avoided the error message.
In the MDE though, it produced a fatal error!!
Fatal-error.bmp
ASKER
I'm relatively new to MDE files.... I'd welcome comments about what problems / issues / design approaches are required.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hmm... the MDE is still bombing out with a fatal error. Although not with the MDB
before you create an mde make sure that the mdb compiles without error
DEBUG>Compile
DEBUG>Compile
add codes to the save process to trap any cancellation which will cause the filename to be equal to ""
then create another .mde and replace the old ones