From: John Nurick on
Thanks for the feedback, Rob.

On Fri, 16 Jun 2006 12:07:49 +1000, "Rob Parker"
<NOSPAMrobpparker(a)optusnet.com.au.REMOVETHIS> wrote:

>Hi John and Roy,
>
>I can't say for certain, but it appears (from carefully watching the Process
>tab in Windows task Manager) that the TransferSpreadsheet method does not
>invoke an Excel process.
>
>However, following Roy's comment, I tried commenting out the
>TransferSpreadsheet line in the innermost loop of my , and simply
>debug.printing the name of each sheet. In that case, the first instance of
>Excel IS removed when the loop finishes.
>
>Thanks, Roy. Now I know what the real problem is. And, as I said in my
>last reply to John, the function to get the sheet names without opening
>Excel allows me to do what I need to.
>
>Rob
>
>
>"John Nurick" <j.mapSoN.nurick(a)dial.pipex.com> wrote in message
>news:0h7392l3hl5shh497ucvg7ehqhma8q8qqd(a)4ax.com...
>> I'd wondered about that too. TransferSpreadsheet uses the Excel ISAM
>> which - as far as I know - doesn't invoke an instance of Excel; but I've
>> never got round to working out how to confirm this (short of setting up
>> a machine with Access but not Excel and then trying to import from a
>> workbook file).
>>
>> On Thu, 15 Jun 2006 18:16:27 +0200, RoyVidar <roy_vidarNOSPAM(a)yahoo.no>
>> wrote:
>>
>>>Rob Parker wrote in message <#QSGtn4jGHA.4368(a)TK2MSFTNGP03.phx.gbl> :
>>>[snip]
>>>> The issue of why Set xlApp =
>>>> Nothing fails to close the Excel process still remains.
>>>[snip]
>>>
>>>I *think* the challenge stems from accesing the same file both through
>>>an automated instance of Excel, and through the transfer-thingie at the
>>>same time. Either both of them invokes Excel, or the usage of both
>>>methods on the same file creates the hiccup (methinks).
>>>
>>>To use automation to retrieve the workseet names, I think I'd stuff
>>>them
>>>(the sheet names) into for instance an array, then close/quit Excel
>>>before attempting to use the transfer-thingie.
>>>
>>>It could be a possibility some strategically placed DoEvents could
>>>yield
>>>sufficient to clean up between attempts (though I doubt it).
>>
>> --
>> John Nurick [Microsoft Access MVP]
>>
>> Please respond in the newgroup and not by email.
>

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
From: Rob Parker on
You're welcome. I figure that every little bit helps, for everyone who
might be following this.

My problem is trying to remember all the little bits ;-)

Rob

"John Nurick" <j.mapSoN.nurick(a)dial.pipex.com> wrote in message
news:s1f492tti8gfcnjnse66hm0aqq2sd9jvm0(a)4ax.com...
> Thanks for the feedback, Rob.
<snip>


From: John Nurick on
On Fri, 16 Jun 2006 15:22:03 +1000, "Rob Parker"
<NOSPAMrobpparker(a)optusnet.com.au.REMOVETHIS> wrote:

>My problem is trying to remember all the little bits ;-)

Isn't that what databases are for? <g>

--
John Nurick [Microsoft Access MVP]

Please respond in the newgroup and not by email.
First  |  Prev  | 
Pages: 1 2 3
Prev: ADHResize2K error
Next: Highlight Current Row