[AccessD] Mixed Versions

[Rocky Smolin]

So here's an odd problem.  I'm trying to set up a virtual machine with )2013
minus Access.  But unlike every other previous Office, I don't get an
opportunity to select the apps I want.  It just installs the whole thing. :(

Am I missing something?

R
 

-----Original Message-----
From: Rocky Smolin [mailto:rockysmolin at bchacc.com] 
Sent: Sunday, August 02, 2015 2:23 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Mixed Versions

Oh yeah - the old 32/64 bit gotcha.  Forgot all about that one.  No it's not
O365 (AFAIK, I should verify but I'd bet a dollar they're not).  

I'm trying right now to set up a virtual machine O2013 minus Access & Access
2003.  See if I can duplicate the problem.

Tks

Rocky
 

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim
Dettman
Sent: Sunday, August 02, 2015 2:18 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Mixed Versions

Rocky,

 The late binding should work fine...

 Their not using Office 365 web apps are they?   The other gotcha would be
if their using Office 2013 64 bit edition.  Your code is making 32 bit
calls.   If they are tell them to switch to the 32 bit edition (they'll be a
lot happier in the long run).

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Rocky Smolin
Sent: Sunday, August 02, 2015 04:10 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Mixed Versions

Dear List:
 
I created an app for a client in A2003 that exports stuff to Excel but using
VBA not the Transfer Spreadsheet function.  I used early binding because
that seems to work - even when the target machine has Office 2007 or 2010 -
the reference seems to resolve OK to the version excel on that machine.
 
However, the client recently upgraded to O2013 but without Access.  So
they're using Excel 2013 with Access 2003.  And of course, the export broke.
I thought that the solution would be to switch to late binding. Which works
on my O2003 machine fine.  But still does not work on the clients mixed
version machine.
 
It blows up on the line of code (but unfortunately I cannot find the email
that has the error message):
 
    objXLApp.Workbooks.Open Me.txtOutputFileName

The objects are DIMmed:
 
Dim objXLApp As Object
Dim objXLBook As Object
Dim objXLWS As Object

and the code snip is:
 
    Call CopyFileA(Me.txtRecievingInspectionCutStockTemplate,
Me.txtOutputFileName, False)

    Set objXLApp = CreateObject("Excel.Application")
    objXLApp.Workbooks.Open Me.txtOutputFileName
    Set objXLWS = objXLApp.ActiveSheet

where txtOutputFileName has the path and file name to be opened.
 
I'll try to get some more info but in the meantime is there some change I
have to make to syntax in  objXLApp.Workbooks.Open for Excel 2013? 
 
MTIA
 
Rocky
 
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com