Acc03 - Reports giving 2501. Worked in Acc02 1

[AlanKW]

History and environment:
Our office went through a rollout of a new image upgrading Win2K w/ full versions of Acc97 to WinXP/Runtime Acc03. On a development machine I had a WindowsXP and Acc02/XP. Full install, no corpate image mucky muck. I upgraded & tweaked the Front End of the databases to the 2002 format. Backend is still 97. End users are working great - not a peep.

Issue:
Yesterday, I got the same image of the user, but received the full version of Access instead of the Runtime. Everything seemed to be fine until I ran a report from a form. I received a error 2501 - This process has been cancelled. I click on debug and its one line docmd.openreport "blah blah", acpreview

I close out and go to the Database window and click on Design of a different report. I get the hourglass for a split second then nothing. I double click - nothing. I cant even create a new report! I look at the other object types (tables, queries, etc..) they all appear to be behaving normally.

I copy the database locally - no difference. I log out of the domain and log on locally using an ID that has "DEBUGGER" rights, and I can do reports again! I add domain ID to the Debugger Group and log back into the domain, No reports. I go back and put myself into the Machine Administrator group and don't notice a difference in reporting.

I have no doubt that there is some sort of setting that Corporate has in their image that was done accidentally. They arent crazy about Access and dont use it much, so I'm sure that it wasnt intentional and blocking reports would be just be plain silly.

I made a simple dumy database on my machine using my domain login and was not able to do anything with reports. So its not just older databases.

Does this make sense to anyone? Anyone seen anythig like this? What is different about reports than any other object?

Let me risk being rude for 1 second to restate that the users using the runtime version can run the reports, its only me using the full version that cannot (or design then)

 

[dhookom]

This all makes sense to me if you have not specified a default printer. If you think you have one set up as default then unselect it and then re-select the default.

Duane
MS Access MVP
Find out how to get great answers faq219-2884.

 

[AlanKW]

Ok - this is weird! I DID have a default printer yesterday as I was printing out other things. Last night at the advise of Corporate we

Uninstalled Access
Uninstalled Runtime
Deleted my local profile
Installed Access

(runtime was part of the image and Access was installed after the image) We went into Design mode of a report, Did a cummulative back pat and called it a night. Come in this morning and start getting my computer back to what I want (favorites, icon placement, installing printers) and BAM - no more design mode! But I did so many things at once, w/o testing, I hadnt isolated it to the printer yet.

I deleted my profile again and did a more deliberate configue/test/configure/test routine, and as it turns out that if the HP Laserjet 4050 is the default printer, I cannot do reports. If its the 5si then I can. I'm waiting for the IT guy to come in, and I remember him saying in the past that he's had driver issues with some of the printers as we only have NT4 in the server room and has not been able to get some 2000/XP drivers installed on it.

So I'm guessing that its a server/driver issue. Thank you DHookom for getting me looking in the right direction. Hope my pain saves someone some time.

 

[vitaminD12]

I have been having identical problem. Manipulating with default printers solved the isue. Thx a ton!