Comments on: Access 2010 macros http://itknowledgeexchange.techtarget.com/itanswers/access-2010-macros/ Fri, 24 May 2013 02:38:15 +0000 hourly 1 By: danna http://itknowledgeexchange.techtarget.com/itanswers/access-2010-macros/#comment-87495 danna Thu, 03 Feb 2011 16:32:09 +0000 #comment-87495 Chippy088, Thanks for answering my dilemma. I did put in a close table at the end of the macro once but I still got the same error.
I am a little new to the ACCESS 2010 screens and haven’t quite figured out where (or how) to use their debug report yet. I will try it though.
My complete macro is as follows:
BUILD TEMPORARY TABLE CALLED FillerMaterialStatusReport
OpenQuery
Query Name MQry-Filler MaterialReleaseInfo
View Datasheet
Mode Edit
CloseQuery
Query Name: MQry-Filler MaterialReleaseInfo
Save No
BUILD RELEASE REPORT
OpenReport
Report Name: Release Report
View: Report
(no filters or conditions specified)
EMAIL RELEASE REPORT
If [Reports]![Release Report]![Latest Date Released] Is Not Null Then
EMailDatabaseObject
Type: Report
Name: Release Report
Format: RTF
To
Cc
Bcc
Subject Filler Material Release Report
Message: (blank)
Edit message YES
PRINT RELEASE REPORT
OpenReport
Report Name: Release Report
View: Print
(no filters or conditions specified)
CloseWindow
Type: Report
Name: Release Report
Save: Prompt
End If
BUILD REJECT REPORT
OpenReport
Report Name Reject Report
View Report
(no filters or conditions specified)
EMAIL REJECT REPORT
If [Reports]![Reject Report]![Passed]="NO" Then
EMailDatabaseObject
Type: Report
Name: Reject Report
Format: RTF
To
Cc
Bcc
Subject Filler Material Reject Report
Message Reject materail. Please contact vendor for correctie action.
Edit message Yes
PRINT REJECT REPORT
OpenReport
Report Name: Reject Report
View: Print
(no filters or conditions specified)
CloseWindow
Type: Report
Name: Reject Report
Save: Prompt
End If 

]]>
	
	
		By: chippy088
		http://itknowledgeexchange.techtarget.com/itanswers/access-2010-macros/#comment-87492
		chippy088
		Thu, 03 Feb 2011 15:38:37 +0000
		#comment-87492
		
		We need to see the whole of the macro code to make any suggestions.


Without looking at the code, I’d suggest closing the table and report in the macro. It seems it is terminating abnormally with the tables and report still left open, that’s why you have to manually close it down.


Do you get a debug report from the macro? That might give more suggestions of what is wrong.

]]>