User Profile
Dino55
Copper Contributor
Joined Sep 05, 2022
User Widgets
Recent Discussions
Access PDF report fails on second page and sub-report crashes Access
One of many legacy RTF reports changed to PDF would crash Access when run as a scheduled task but ran OK in developer mode (O365 16.0.14931.20604). I have a work-around, so this post is for others who may have the same issue. The report had a sub-report and crashing stopped when this was deleted. The report printed one page OK and failed on the first line of next page. It was not data related as I doubled the detail line row height and it was always the second page. I tried deleting the page heading; simplifying the query and copying to another DB without impacting the error - it always runs OK when started with shift key. To test, the report was run with a batch file (I am old and don't talk PowerShell) and it would run OK if the .bat was opened with shift key and Autoexec run. By chance I executed the report twice and it worked OK the second time. My work-around (not elegant but enough time has been wasted) is to run a single page PDF report with one line of text "this is a dummy report" before running this report and it works every time.741Views0likes0CommentsRe: Access doesn't close properly. A remaining background process can only be terminated in task manager
It is not my application but an ancient legacy one that started leaving orphaned tasks. My only change was to delete one quit command in a sub-function which was already covered in the initial autoexe function and not needed.4.4KViews0likes1CommentRe: Access doesn't close properly. A remaining background process can only be terminated in task manager
Not all of our apps were leaving tasks behind. If quit was NOT in the same function called via Autoexec then the would be an orphan task. An hourly scheduled task which was problematic stopped producing orphans when its quit was moved into the top level function. (Access 365)4.4KViews0likes3Comments
Recent Blog Articles
No content to show