access runtime 2010 vba application printer error

#ACCESS RUNTIME 2010 VBA APPLICATION PRINTER ERROR HOW TO#
#ACCESS RUNTIME 2010 VBA APPLICATION PRINTER ERROR INSTALL#
#ACCESS RUNTIME 2010 VBA APPLICATION PRINTER ERROR UPDATE#
#ACCESS RUNTIME 2010 VBA APPLICATION PRINTER ERROR CODE#

Docmd.OpenReport works if the report is previewed, but not if it is opened straight to print. To use the correct printer, you must use the supplied function, OpenTheReport(). That can be done by opening the report in design view, and manipulating PrtMip. The utility does not let the user choose paper sizes. Albert Kallal has one for earlier versions: Access 97 or Access 2000. The utility works only with Access 2002 and later. The utility remembers the choice, and uses that printer for that report in future. To assign a printer, all the user has to do is preview the report, and click the custom Set Printer toolbar button. The function checks to see if the user has assigned a particular printer for the report, and assigns the Printer before the report opens. The utility has a function named OpenTheReport() to use instead of DoCmd.OpenReport.

#ACCESS RUNTIME 2010 VBA APPLICATION PRINTER ERROR CODE#

You can also view the code from this utility.

#ACCESS RUNTIME 2010 VBA APPLICATION PRINTER ERROR HOW TO#

The utility also illustrates how to manipulate the Printer object and the Printers collection introduced in Access 2002.Ĭlick to download the utility (30KB, Access 2002/3 mdb format, zipped). The utility works with MDE files and runtime versions also. Whenever they open the report, it is sent to that printer. This utility lets the end user assign one of their printers to each report. You can design a report to use one of your printers by choosing Page Setup from the Page Setup ribbon (Access 2010), the Report Tools ribbon (Access 2007), or the File menu (previous versions.) But that approach is useless if others use your report: you do not know what printers they will have installed. I have also tried changing the OLE timeout setting from 30 to 999 but it did not make any difference.Microsoft Access: Applications and Utilities

#ACCESS RUNTIME 2010 VBA APPLICATION PRINTER ERROR INSTALL#

I also googled and found a link to a Microsoft Hotfix for exactly this issue, but when I tried to install it, it said that it could not find any relevant application installed on my pc. I have tried compacting and repairing the database, and adding Indices to the join fields being used in the query, but to no avail. If I comment out the rogue query and press F5, then the process moves on 2 more queries before failing again with the same error message. I am told that it is not necessarily the same query that falls over each time and I am also told that occasionally just pressing F5 in the Debug window will eventually get the query to run, although I've not seen that myself.

#ACCESS RUNTIME 2010 VBA APPLICATION PRINTER ERROR UPDATE#

The report that I am running today is falling over consistently at a particular update query. The 'UpdateTables' subroutine in Access is just a list of about 60 DoCmd.OpenQuery calls. Set acApp = CreateObject('Access.Application')ĪcApp.OpenCurrentDatabase (m_strDBCopyPath & m_strDBCopyName) The process is kicked off from within Excel VBA, which opens our Master database, imports the dataset to the main table, then calls an Access VBA sub-routine, which in turn calls about 60 Access update queries and make-table queries one after the other, using docmd.openquery. Since XP is no longer supported we really need to get the issue with Access 2013 resolved. It's only our newer, Windows 7 pcs with Access 2013 which have the problem. The solution (up to now) has been to run the same job on an old Windows XP machine, running Access 2003, which seems to be able to handle even the largest datasets. The majority of the time this runs fine, but if the initial dataset is large (> 100,000 rows) then we sometimes hit an error 'Run Time error 3035 - System Resource exceeded'. One thing I have inherited is an Access database which we use on a daily basis to run reports for customers.Įach time it's used, a customer-specific dataset is imported to a table, then update and make-table queries are run to perform various calculations before the data is copied back into Excel to create the final report. I might become a regular poster on here as I have a new job which is supporting a miscellany of Access and Excel applications, something I have not done for a few years now.

Access runtime 2010 vba application printer error