Jim Dettman
jimdettman at verizon.net
Wed Jan 14 18:59:00 CST 2015
As John said, with late binding you should be fine. You would not get any kind of error until you hit the routine that uses Excel Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Brad Marks Sent: Wednesday, January 14, 2015 04:06 PM To: Access Developers discussion and problem solving Subject: [AccessD] Access 2007 Reporting Application - Problems with Excel not Installed on Server All, We have a Reporting Application that was built with Access 2007. This application is used by our end-users for "on demand" reports and the same application is used to generate nightly automated reports. These automated reports are run on our server, using Access 2007 Runtime. This application has worked nicely for over three years. Recently, I have been working with "Windows Automation" to push some of the key data from Access to Excel in order to satisfy an outside accounting firm's requirements. This new feature is now working nicely (on a desktop PC that has Excel). Our accounting people are super-impressed. Here's the catch. We do not have Excel installed on our server. Currently there is no need to use the new "Windows Automation" (Access controlling Excel) features for the reports that are run on the server. These reports will only be needed on desktops that have Excel. Is there a way to enable this Access application to run on the Server where Excel is not installed. Again, the automated reports that are run on the server do not use the new "Windows Automation" features that are used on the desktops that have Excel. Thanks, Brad -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com