Reports Lost in Packaged db runtime

[capnmark]

I have packaged 2 different dbs with developer tools package / deploy. Both dbs work great under access. Both work fine as far as form and data manipulation & vb. Neither will show any of the reports in either database.
This is driving me nuts. It's like there not even there.

Have tried various solutions. Closing the calling form, changing form prop. to modal=false, in each instance the forms will exit or yield control but no reports are there.
no errors are generated.

Thanks
Mark

 

[Hap007]

Dear Mark,

I have 2 thoughts/comments for you.

1) Are you setting the reports to the 'default' printer.
You normally need to set it up this way when you deploy to another PC.

2) I have seen instances where a report works fine on one PC running access, but move that same DB to another PC, and the report fails. I have seen reports that will print fine on a PC, but default to a different page size on another PC.

When item 2 occurs, it is some times due to a printer driver not working correctly, or perhaps a copy of access that has gone bad, or I have seen Access XP (full version) installed on a PC, and then a 'Runtime only' earlier version of an Access app is installed second, and everything goes bad.

Try running access on the PC that is giving you trouble, create a simple database and report and see if access will let you create and print that report.

In summary, I have been there before, it is frustrating, and I can not offer any one fix. But I thought I would let you know that I too have had those type of problems. And it has happened more than once, with different versions of Access, from Access 97 to Access XP.

Good Luck,
Hap...

Access Developer

http://www.fcs-software.com/fcsaccessdev.html

Access based Add-on Solutions
Access Consultants forum

http://www.tek-tips.com/groups/accessDevelopers

 

[capnmark]

This is a packaged database running via Access Runtime on a friends test computer.

I have not configured it to any particular printer. I'll look into these issues and see if I can digest it.

Thanks for your input
Mark