By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,728 Members | 1,120 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,728 IT Pros & Developers. It's quick & easy.

Error with MDB but not with MDE in Runtime

P: n/a
sj
I am using Access 03 to develop a Quotation system and has this
strange enconter.

On computer with Full Access Ver.
---------------------------------------------------
The MDB program works well, and also when simulated of /runtime.

On computer runntion on Runtime
-------------------------------------------------
Error occur with MDB but not with converted MDE.

Detail of error:
--------------------
"Execution of this application has stopped due to a run-time error.
This application can't continue and will be shut down."

Happens after this code:
----------------------------------
DoCmd.Close acReport, stPubDocName

Situation when it happens:
--------------------------------------
When there is more than one QuotationDetails in the Quotation report.
Please help.

May 25 '07 #1
Share this Question
Share on Google+
2 Replies

P: n/a
ARC
You might want to put an error handling routine in the On_Close event of the
report in question. That way, when it hits in the error in the on_close,
your message will come up, and the system will continue on without erroring
all the way out...

"sj" <se*********@gmail.comwrote in message
news:11********************@z28g2000prd.googlegrou ps.com...
>I am using Access 03 to develop a Quotation system and has this
strange enconter.

On computer with Full Access Ver.
---------------------------------------------------
The MDB program works well, and also when simulated of /runtime.

On computer runntion on Runtime
-------------------------------------------------
Error occur with MDB but not with converted MDE.

Detail of error:
--------------------
"Execution of this application has stopped due to a run-time error.
This application can't continue and will be shut down."

Happens after this code:
----------------------------------
DoCmd.Close acReport, stPubDocName

Situation when it happens:
--------------------------------------
When there is more than one QuotationDetails in the Quotation report.
Please help.

May 25 '07 #2

P: n/a
On May 25, 8:13 am, "ARC" <a...@andyc.comwrote:
You might want to put an error handling routine in the On_Close event of the
report in question. That way, when it hits in the error in the on_close,
your message will come up, and the system will continue on without erroring
all the way out...

"sj" <sengjin....@gmail.comwrote in message

news:11********************@z28g2000prd.googlegrou ps.com...
I am using Access 03 to develop a Quotation system and has this
strange enconter.
On computer with Full Access Ver.
---------------------------------------------------
The MDB program works well, and also when simulated of /runtime.
On computer runntion on Runtime
-------------------------------------------------
Error occur with MDB but not with converted MDE.
Detail of error:
--------------------
"Execution of this application has stopped due to a run-time error.
This application can't continue and will be shut down."
Happens after this code:
----------------------------------
DoCmd.Close acReport, stPubDocName
Situation when it happens:
--------------------------------------
When there is more than one QuotationDetails in the Quotation report.
Please help.- Hide quoted text -

- Show quoted text -
It sound like a corrupt form to me. Anyway, you should rule out a
corrupt form by setting the /decompile switch as a command line
startup option as below:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "C:\CTDDT
\CTD.mdb" /wrkgrp "C:\CTDDT\CTD.mdw" /user "Administrator" /Excl /
decompile
If that doesn't work create another form and see if the code runs OK
from it.

As a last ditch measure create a new empty .mdb file and import all
the objects from your current .mdb into it.

Good Luck,
Barry
www.witstoronto.ca

May 30 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.