Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.ms-access > #10557 > unrolled thread

Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP

Started byfs <franc.sutherland@googlemail.com>
First post2015-03-31 07:56 -0700
Last post2015-04-27 07:51 -0700
Articles 18 — 3 participants

Back to article view | Back to comp.databases.ms-access

Contents

  Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-03-31 07:56 -0700
    Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP "Phil" <phil@stantonfamily.co.uk> - 2015-03-31 16:35 +0100
      Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-01 04:12 -0700
        Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP "Phil" <phil@stantonfamily.co.uk> - 2015-04-01 13:57 +0100
          Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-02 01:18 -0700
        Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP "Ron Paii" <None@none.com> - 2015-04-01 15:14 -0500
          Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-02 01:20 -0700
            Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-02 02:17 -0700
              Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP "Ron Paii" <None@none.com> - 2015-04-02 07:02 -0500
                Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-07 07:26 -0700
                  Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-08 08:12 -0700
                    Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP "Ron Paii" <None@none.com> - 2015-04-08 15:59 -0500
                      Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-09 02:54 -0700
                        Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP "Ron Paii" <None@none.com> - 2015-04-09 16:02 -0500
                          Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-10 02:36 -0700
                            Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP "Ron Paii" <None@none.com> - 2015-04-10 07:08 -0500
                              Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-14 08:47 -0700
                                Re: Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP fs <franc.sutherland@googlemail.com> - 2015-04-27 07:51 -0700

#10557 — Word menus frozen after mail merge with Office 2003 on Windows 7 but not XP

Fromfs <franc.sutherland@googlemail.com>
Date2015-03-31 07:56 -0700
SubjectWord menus frozen after mail merge with Office 2003 on Windows 7 but not XP
Message-ID<7c4bbce9-f4a1-4922-b18d-632a2bed4f39@googlegroups.com>
Hi all,

I have an Access 2003 database doing a mail merge to Word 2003.  It works fine on two Windows XP machines but not with Windows 7.

On the Windows 7 machines, a Word application opens and the mail merge data is passed (via a txt file) into the .doc file.  But the Word Window doesn't take the focus and the user has to click on it in the taskbar (which doesn't happen with the XP machines).  

As well as that, the menus are frozen/inaccessible and the only button that works is the big red x in the top right.  When the user clicks that they are given the Save As option.  They can save the file and re-open it and edit as normal.

My question is what is happening when the initial merge is happening and the menus are frozen on the Windows 7 machines?  Is this a permissions issue to do with Windows 7 and programs activating each other using VBA?

I'd really appreciate any suggestions.  It's been dragging on for ages and I can't find any information about it anywhere.

Thanks!

[toc] | [next] | [standalone]

#10558

From"Phil" <phil@stantonfamily.co.uk>
Date2015-03-31 16:35 +0100
Message-ID<mfeeri$lt8$1@speranza.aioe.org>
In reply to#10557
On 31/03/2015 15:56:52, fs wrote:
> Hi all,
> 
> I have an Access 2003 database doing a mail merge to Word 2003. It works f
> ine on two Windows XP machines but not with Windows 7.
> 
> On the Windows 7 machines, a Word application opens and the mail merge
> data is passed (via a txt file) into the .doc file. But the Word Window
> doesn' t take the focus and the user has to click on it in the taskbar
> (which does n't happen with the XP machines).
> 
> As well as that, the menus are frozen/inaccessible and the only button
> that works is the big red x in the top right. When the user clicks that
> they a re given the Save As option. They can save the file and re-open it
> and edi t as normal.
> 
> My question is what is happening when the initial merge is happening and
> th e menus are frozen on the Windows 7 machines? Is this a permissions
> issue to do with Windows 7 and programs activating each other using VBA?
> 
> I'd really appreciate any suggestions. It's been dragging on for ages and
> I can't find any information about it anywhere.
> 
> Thanks!
> 

Assuming you are usimg VBA do you have things like

    Dim WordApp             As Object       ' Word.Applicaton

    Set WordApp = GetObject(, "Word.Application")

    WordApp.Visible = True
    WordApp.Activate
    WordApp.WindowState = 0          'wdWindowStateRestore

Phil

---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com

[toc] | [prev] | [next] | [standalone]

#10559

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-01 04:12 -0700
Message-ID<03fd8ddd-a1f3-46e4-99f9-6a604fccde26@googlegroups.com>
In reply to#10558
On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> On 31/03/2015 15:56:52, fs wrote:
> > Hi all,
> > 
> > I have an Access 2003 database doing a mail merge to Word 2003. It works f
> > ine on two Windows XP machines but not with Windows 7.
> > 
> > On the Windows 7 machines, a Word application opens and the mail merge
> > data is passed (via a txt file) into the .doc file. But the Word Window
> > doesn' t take the focus and the user has to click on it in the taskbar
> > (which does n't happen with the XP machines).
> > 
> > As well as that, the menus are frozen/inaccessible and the only button
> > that works is the big red x in the top right. When the user clicks that
> > they a re given the Save As option. They can save the file and re-open it
> > and edi t as normal.
> > 
> > My question is what is happening when the initial merge is happening and
> > th e menus are frozen on the Windows 7 machines? Is this a permissions
> > issue to do with Windows 7 and programs activating each other using VBA?
> > 
> > I'd really appreciate any suggestions. It's been dragging on for ages and
> > I can't find any information about it anywhere.
> > 
> > Thanks!
> > 
> 
> Assuming you are usimg VBA do you have things like
> 
>     Dim WordApp             As Object       ' Word.Applicaton
> 
>     Set WordApp = GetObject(, "Word.Application")
> 
>     WordApp.Visible = True
>     WordApp.Activate
>     WordApp.WindowState = 0          'wdWindowStateRestore
> 
> Phil
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> http://www.avast.com

Hi Phil,
Thanks for replying.

I've tried a couple of ways.

The first one was
---------------------------------------------------------------------------
Dim ow As Word.Application
Dim xDoc As Word.Document
dim xFilename as string
dim xDatasource as string

xFilename = "C:\myDoc.doc"
xDatasource = "C:\myData.csv"
Set ow = CreateObject("Word.Application")
Set xDoc = ow.Documents.Open(xFilename)

ow.Documents(x_filename).ActiveWindow.Activate
ow.Application.WindowState = wdWindowStateMaximize

With Xdoc
    .MailMerge.OpenDataSource (xDatasource)
    .MailMerge.Destination = wdSendToNewDocument
    .MailMerge.Execute
    .ActiveWindow.Activate
    .Windows.Application.WindowState = wdWindowStateMaximize
    .Close
End With

ow.Visible = True

-----------------------------------------------------------------------------

The second method was more involved but, I thought, bomb-proof way of bringing any application into focus.  It involves using Windows API calls to read the application's window caption and bring it forward.

Here's the link for it - http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground

-----------------------------------------------------------------------------

Both of these methods work on the XP machines but neither works on the Windows 7 machines.  

Any ideas?

Thanks, Franc.

[toc] | [prev] | [next] | [standalone]

#10560

From"Phil" <phil@stantonfamily.co.uk>
Date2015-04-01 13:57 +0100
Message-ID<mfgpvc$t8h$1@speranza.aioe.org>
In reply to#10559
On 01/04/2015 12:12:14, fs wrote:
> On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
>> On 31/03/2015 15:56:52, fs wrote:
>> > Hi all,
>> >
>> > I have an Access 2003 database doing a mail merge to Word 2003. It works f
>> > ine on two Windows XP machines but not with Windows 7.
>> >
>> > On the Windows 7 machines, a Word application opens and the mail merge
>> > data is passed (via a txt file) into the .doc file. But the Word Window
>> > doesn' t take the focus and the user has to click on it in the taskbar
>> > (which does n't happen with the XP machines).
>> >
>> > As well as that, the menus are frozen/inaccessible and the only button
>> > that works is the big red x in the top right. When the user clicks that
>> > they a re given the Save As option. They can save the file and re-open it
>> > and edi t as normal.
>> >
>> > My question is what is happening when the initial merge is happening and
>> > th e menus are frozen on the Windows 7 machines? Is this a permissions
>> > issue to do with Windows 7 and programs activating each other using VBA?
>> >
>> > I'd really appreciate any suggestions. It's been dragging on for ages and
>> > I can't find any information about it anywhere.
>> >
>> > Thanks!
>> >
>>
>> Assuming you are usimg VBA do you have things like
>>
>>     Dim WordApp             As Object       ' Word.Applicaton
>>
>>     Set WordApp = GetObject(, "Word.Application")
>>
>>     WordApp.Visible = True
>>     WordApp.Activate
>>     WordApp.WindowState = 0          'wdWindowStateRestore
>>
>> Phil
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> http://www.avast.com
> 
> Hi Phil,
> Thanks for replying.
> 
> I've tried a couple of ways.
> 
> The first one was
> ---------------------------------------------------------------------------
> Dim ow As Word.Application Dim xDoc As Word.Document
> dim xFilename as string
> dim xDatasource as string
> 
> xFilename = "C:\myDoc.doc"
> xDatasource = "C:\myData.csv"
> Set ow = CreateObject("Word.Application")
> Set xDoc = ow.Documents.Open(xFilename)
> 
> ow.Documents(x_filename).ActiveWindow.Activate
> ow.Application.WindowState = wdWindowStateMaximize
> 
> With Xdoc
> .MailMerge.OpenDataSource (xDatasource)
> .MailMerge.Destination = wdSendToNewDocument
> .MailMerge.Execute
> .ActiveWindow.Activate
> .Windows.Application.WindowState = wdWindowStateMaximize
> .Close
> End With
> 
> ow.Visible = True
> 
> -----------------------------------------------------------------------------
> 
> The second method was more involved but, I thought, bomb-proof way of
> bringing any application into focus. It involves using Windows API calls
> to read the application's window caption and bring it forward.
> 
> Here's the link for it -
> http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> 
> -----------------------------------------------------------------------------
> 
> Both of these methods work on the XP machines but neither works on the
> Windows 7 machines.
> 
> Any ideas?
> 
> Thanks, Franc.
> 
> 

Well it works on my windows 7 machine with Access 2010

Try adding in the With Clause (XDoc)
    .Activate

Phil

---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com

[toc] | [prev] | [next] | [standalone]

#10571

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-02 01:18 -0700
Message-ID<363bbdc6-3832-45f0-b1fb-feeeb26f3386@googlegroups.com>
In reply to#10560
On Wednesday, 1 April 2015 13:57:22 UTC+1, Phil  wrote:
> On 01/04/2015 12:12:14, fs wrote:
> > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> >> On 31/03/2015 15:56:52, fs wrote:
> >> > Hi all,
> >> >
> >> > I have an Access 2003 database doing a mail merge to Word 2003. It works f
> >> > ine on two Windows XP machines but not with Windows 7.
> >> >
> >> > On the Windows 7 machines, a Word application opens and the mail merge
> >> > data is passed (via a txt file) into the .doc file. But the Word Window
> >> > doesn' t take the focus and the user has to click on it in the taskbar
> >> > (which does n't happen with the XP machines).
> >> >
> >> > As well as that, the menus are frozen/inaccessible and the only button
> >> > that works is the big red x in the top right. When the user clicks that
> >> > they a re given the Save As option. They can save the file and re-open it
> >> > and edi t as normal.
> >> >
> >> > My question is what is happening when the initial merge is happening and
> >> > th e menus are frozen on the Windows 7 machines? Is this a permissions
> >> > issue to do with Windows 7 and programs activating each other using VBA?
> >> >
> >> > I'd really appreciate any suggestions. It's been dragging on for ages and
> >> > I can't find any information about it anywhere.
> >> >
> >> > Thanks!
> >> >
> >>
> >> Assuming you are usimg VBA do you have things like
> >>
> >>     Dim WordApp             As Object       ' Word.Applicaton
> >>
> >>     Set WordApp = GetObject(, "Word.Application")
> >>
> >>     WordApp.Visible = True
> >>     WordApp.Activate
> >>     WordApp.WindowState = 0          'wdWindowStateRestore
> >>
> >> Phil
> >>
> >> ---
> >> This email has been checked for viruses by Avast antivirus software.
> >> http://www.avast.com
> > 
> > Hi Phil,
> > Thanks for replying.
> > 
> > I've tried a couple of ways.
> > 
> > The first one was
> > ---------------------------------------------------------------------------
> > Dim ow As Word.Application Dim xDoc As Word.Document
> > dim xFilename as string
> > dim xDatasource as string
> > 
> > xFilename = "C:\myDoc.doc"
> > xDatasource = "C:\myData.csv"
> > Set ow = CreateObject("Word.Application")
> > Set xDoc = ow.Documents.Open(xFilename)
> > 
> > ow.Documents(x_filename).ActiveWindow.Activate
> > ow.Application.WindowState = wdWindowStateMaximize
> > 
> > With Xdoc
> > .MailMerge.OpenDataSource (xDatasource)
> > .MailMerge.Destination = wdSendToNewDocument
> > .MailMerge.Execute
> > .ActiveWindow.Activate
> > .Windows.Application.WindowState = wdWindowStateMaximize
> > .Close
> > End With
> > 
> > ow.Visible = True
> > 
> > -----------------------------------------------------------------------------
> > 
> > The second method was more involved but, I thought, bomb-proof way of
> > bringing any application into focus. It involves using Windows API calls
> > to read the application's window caption and bring it forward.
> > 
> > Here's the link for it -
> > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> > 
> > -----------------------------------------------------------------------------
> > 
> > Both of these methods work on the XP machines but neither works on the
> > Windows 7 machines.
> > 
> > Any ideas?
> > 
> > Thanks, Franc.
> > 
> > 
> 
> Well it works on my windows 7 machine with Access 2010
> 
> Try adding in the With Clause (XDoc)
>     .Activate
> 
> Phil
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> http://www.avast.com

Hi Phil, OK will try that and report back.

[toc] | [prev] | [next] | [standalone]

#10564

From"Ron Paii" <None@none.com>
Date2015-04-01 15:14 -0500
Message-ID<mfhjht$o2o$1@dont-email.me>
In reply to#10559

"fs" <franc.sutherland@googlemail.com> wrote in message 
news:03fd8ddd-a1f3-46e4-99f9-6a604fccde26@googlegroups.com...
> On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
>> On 31/03/2015 15:56:52, fs wrote:
>> > Hi all,
>> >
>> > I have an Access 2003 database doing a mail merge to Word 2003. It 
>> > works f
>> > ine on two Windows XP machines but not with Windows 7.
>> >
>> > On the Windows 7 machines, a Word application opens and the mail merge
>> > data is passed (via a txt file) into the .doc file. But the Word Window
>> > doesn' t take the focus and the user has to click on it in the taskbar
>> > (which does n't happen with the XP machines).
>> >
>> > As well as that, the menus are frozen/inaccessible and the only button
>> > that works is the big red x in the top right. When the user clicks that
>> > they a re given the Save As option. They can save the file and re-open 
>> > it
>> > and edi t as normal.
>> >
>> > My question is what is happening when the initial merge is happening 
>> > and
>> > th e menus are frozen on the Windows 7 machines? Is this a permissions
>> > issue to do with Windows 7 and programs activating each other using 
>> > VBA?
>> >
>> > I'd really appreciate any suggestions. It's been dragging on for ages 
>> > and
>> > I can't find any information about it anywhere.
>> >
>> > Thanks!
>> >
>>
>> Assuming you are usimg VBA do you have things like
>>
>>     Dim WordApp             As Object       ' Word.Applicaton
>>
>>     Set WordApp = GetObject(, "Word.Application")
>>
>>     WordApp.Visible = True
>>     WordApp.Activate
>>     WordApp.WindowState = 0          'wdWindowStateRestore
>>
>> Phil
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> http://www.avast.com
>
> Hi Phil,
> Thanks for replying.
>
> I've tried a couple of ways.
>
> The first one was
> ---------------------------------------------------------------------------
> Dim ow As Word.Application
> Dim xDoc As Word.Document
> dim xFilename as string
> dim xDatasource as string
>
> xFilename = "C:\myDoc.doc"
> xDatasource = "C:\myData.csv"
> Set ow = CreateObject("Word.Application")
> Set xDoc = ow.Documents.Open(xFilename)
>
> ow.Documents(x_filename).ActiveWindow.Activate
> ow.Application.WindowState = wdWindowStateMaximize
>
> With Xdoc
>    .MailMerge.OpenDataSource (xDatasource)
>    .MailMerge.Destination = wdSendToNewDocument
>    .MailMerge.Execute
>    .ActiveWindow.Activate
>    .Windows.Application.WindowState = wdWindowStateMaximize
>    .Close
> End With
>
> ow.Visible = True
>
> -----------------------------------------------------------------------------
>
> The second method was more involved but, I thought, bomb-proof way of 
> bringing any application into focus.  It involves using Windows API calls 
> to read the application's window caption and bring it forward.
>
> Here's the link for it - 
> http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
>
> -----------------------------------------------------------------------------
>
> Both of these methods work on the XP machines but neither works on the 
> Windows 7 machines.
>
> Any ideas?
>
> Thanks, Franc.
>

Are you storing the file in the base of the "C" drive? Windows can be touchy 
about file in that location, try putting it in a folder.

[toc] | [prev] | [next] | [standalone]

#10572

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-02 01:20 -0700
Message-ID<8da9a32f-538b-48be-8209-b44fbe3ecd12@googlegroups.com>
In reply to#10564
On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:

> > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> >> On 31/03/2015 15:56:52, fs wrote:
> >> > Hi all,
> >> >
> >> > I have an Access 2003 database doing a mail merge to Word 2003. It 
> >> > works f
> >> > ine on two Windows XP machines but not with Windows 7.
> >> >
> >> > On the Windows 7 machines, a Word application opens and the mail merge
> >> > data is passed (via a txt file) into the .doc file. But the Word Window
> >> > doesn' t take the focus and the user has to click on it in the taskbar
> >> > (which does n't happen with the XP machines).
> >> >
> >> > As well as that, the menus are frozen/inaccessible and the only button
> >> > that works is the big red x in the top right. When the user clicks that
> >> > they a re given the Save As option. They can save the file and re-open 
> >> > it
> >> > and edi t as normal.
> >> >
> >> > My question is what is happening when the initial merge is happening 
> >> > and
> >> > th e menus are frozen on the Windows 7 machines? Is this a permissions
> >> > issue to do with Windows 7 and programs activating each other using 
> >> > VBA?
> >> >
> >> > I'd really appreciate any suggestions. It's been dragging on for ages 
> >> > and
> >> > I can't find any information about it anywhere.
> >> >
> >> > Thanks!
> >> >
> >>
> >> Assuming you are usimg VBA do you have things like
> >>
> >>     Dim WordApp             As Object       ' Word.Applicaton
> >>
> >>     Set WordApp = GetObject(, "Word.Application")
> >>
> >>     WordApp.Visible = True
> >>     WordApp.Activate
> >>     WordApp.WindowState = 0          'wdWindowStateRestore
> >>
> >> Phil
> >>
> >> ---
> >> This email has been checked for viruses by Avast antivirus software.
> >> http://www.avast.com
> >
> > Hi Phil,
> > Thanks for replying.
> >
> > I've tried a couple of ways.
> >
> > The first one was
> > ---------------------------------------------------------------------------
> > Dim ow As Word.Application
> > Dim xDoc As Word.Document
> > dim xFilename as string
> > dim xDatasource as string
> >
> > xFilename = "C:\myDoc.doc"
> > xDatasource = "C:\myData.csv"
> > Set ow = CreateObject("Word.Application")
> > Set xDoc = ow.Documents.Open(xFilename)
> >
> > ow.Documents(x_filename).ActiveWindow.Activate
> > ow.Application.WindowState = wdWindowStateMaximize
> >
> > With Xdoc
> >    .MailMerge.OpenDataSource (xDatasource)
> >    .MailMerge.Destination = wdSendToNewDocument
> >    .MailMerge.Execute
> >    .ActiveWindow.Activate
> >    .Windows.Application.WindowState = wdWindowStateMaximize
> >    .Close
> > End With
> >
> > ow.Visible = True
> >
> > -----------------------------------------------------------------------------
> >
> > The second method was more involved but, I thought, bomb-proof way of 
> > bringing any application into focus.  It involves using Windows API calls 
> > to read the application's window caption and bring it forward.
> >
> > Here's the link for it - 
> > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> >
> > -----------------------------------------------------------------------------
> >
> > Both of these methods work on the XP machines but neither works on the 
> > Windows 7 machines.
> >
> > Any ideas?
> >
> > Thanks, Franc.
> >
> 
> Are you storing the file in the base of the "C" drive? Windows can be touchy 
> about file in that location, try putting it in a folder.

Hi Ron, 
Sorry, no I'm not storing either file in the C drive.  I just put that to show they were locally stored.  The actual path was a bit long, I thought it would be easier to just put something like that.  My apologies for creating the confusion.
Thanks, Franc.

[toc] | [prev] | [next] | [standalone]

#10573

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-02 02:17 -0700
Message-ID<5cb44ce2-b536-489d-a32d-3f8c257a5831@googlegroups.com>
In reply to#10572
On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
> 
> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> > >> On 31/03/2015 15:56:52, fs wrote:
> > >> > Hi all,
> > >> >
> > >> > I have an Access 2003 database doing a mail merge to Word 2003. It 
> > >> > works f
> > >> > ine on two Windows XP machines but not with Windows 7.
> > >> >
> > >> > On the Windows 7 machines, a Word application opens and the mail merge
> > >> > data is passed (via a txt file) into the .doc file. But the Word Window
> > >> > doesn' t take the focus and the user has to click on it in the taskbar
> > >> > (which does n't happen with the XP machines).
> > >> >
> > >> > As well as that, the menus are frozen/inaccessible and the only button
> > >> > that works is the big red x in the top right. When the user clicks that
> > >> > they a re given the Save As option. They can save the file and re-open 
> > >> > it
> > >> > and edi t as normal.
> > >> >
> > >> > My question is what is happening when the initial merge is happening 
> > >> > and
> > >> > th e menus are frozen on the Windows 7 machines? Is this a permissions
> > >> > issue to do with Windows 7 and programs activating each other using 
> > >> > VBA?
> > >> >
> > >> > I'd really appreciate any suggestions. It's been dragging on for ages 
> > >> > and
> > >> > I can't find any information about it anywhere.
> > >> >
> > >> > Thanks!
> > >> >
> > >>
> > >> Assuming you are usimg VBA do you have things like
> > >>
> > >>     Dim WordApp             As Object       ' Word.Applicaton
> > >>
> > >>     Set WordApp = GetObject(, "Word.Application")
> > >>
> > >>     WordApp.Visible = True
> > >>     WordApp.Activate
> > >>     WordApp.WindowState = 0          'wdWindowStateRestore
> > >>
> > >> Phil
> > >>
> > >> ---
> > >> This email has been checked for viruses by Avast antivirus software.
> > >> http://www.avast.com
> > >
> > > Hi Phil,
> > > Thanks for replying.
> > >
> > > I've tried a couple of ways.
> > >
> > > The first one was
> > > ---------------------------------------------------------------------------
> > > Dim ow As Word.Application
> > > Dim xDoc As Word.Document
> > > dim xFilename as string
> > > dim xDatasource as string
> > >
> > > xFilename = "C:\myDoc.doc"
> > > xDatasource = "C:\myData.csv"
> > > Set ow = CreateObject("Word.Application")
> > > Set xDoc = ow.Documents.Open(xFilename)
> > >
> > > ow.Documents(x_filename).ActiveWindow.Activate
> > > ow.Application.WindowState = wdWindowStateMaximize
> > >
> > > With Xdoc
> > >    .MailMerge.OpenDataSource (xDatasource)
> > >    .MailMerge.Destination = wdSendToNewDocument
> > >    .MailMerge.Execute
> > >    .ActiveWindow.Activate
> > >    .Windows.Application.WindowState = wdWindowStateMaximize
> > >    .Close
> > > End With
> > >
> > > ow.Visible = True
> > >
> > > -----------------------------------------------------------------------------
> > >
> > > The second method was more involved but, I thought, bomb-proof way of 
> > > bringing any application into focus.  It involves using Windows API calls 
> > > to read the application's window caption and bring it forward.
> > >
> > > Here's the link for it - 
> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> > >
> > > -----------------------------------------------------------------------------
> > >
> > > Both of these methods work on the XP machines but neither works on the 
> > > Windows 7 machines.
> > >
> > > Any ideas?
> > >
> > > Thanks, Franc.
> > >
> > 
> > Are you storing the file in the base of the "C" drive? Windows can be touchy 
> > about file in that location, try putting it in a folder.
> 
> Hi Ron, 
> Sorry, no I'm not storing either file in the C drive.  I just put that to show they were locally stored.  The actual path was a bit long, I thought it would be easier to just put something like that.  My apologies for creating the confusion.
> Thanks, Franc.

Hi Phil,
I tried that but it didn't change anything I'm afraid.
I took your idea though and added a couple of new lines

ow.Activate
ow.Application.WindowState = wdWindowStateMaximize

So the complete code now looks like this
 
--------------------------------------------------------
Dim ow As Word.Application
Dim xDoc As Word.Document
dim xFilename as string
dim xDatasource as string

xFilename = "C:\myDoc.doc"
xDatasource = "C:\myData.csv"
Set ow = CreateObject("Word.Application")
Set xDoc = ow.Documents.Open(xFilename)

ow.Documents(x_filename).ActiveWindow.Activate
ow.Application.WindowState = wdWindowStateMaximize

With Xdoc
   .MailMerge.OpenDataSource (xDatasource)
   .MailMerge.Destination = wdSendToNewDocument
   .MailMerge.Execute
   .ActiveWindow.Activate
   .Windows.Application.WindowState = wdWindowStateMaximize
   .Close
End With

    ow.Visible = True
    ow.Activate
    ow.Application.WindowState = wdWindowStateMaximize
set ow = Nothing '(this was there already, just forgot to put into the post)
---------------------------------------------------------------

With these new lines the problem Windows 7 machine reacts a bit differently.  Now Word opens in the taskbar and flashes and when the user clicks on it the menus are not frozen and they can go ahead with editing.  It's progress, but not quite the full solution!

The user has reported that he had the same response of only getting the flashing button in the taskbar when he was using the database on a Windows XP machine but which was XP home edition.  The two XP machines which work as desired are XP Pro machines.  Does this help?

Could the user have changed a Windows setting which stops it happening?

[toc] | [prev] | [next] | [standalone]

#10574

From"Ron Paii" <None@none.com>
Date2015-04-02 07:02 -0500
Message-ID<mfjb3o$665$1@dont-email.me>
In reply to#10573

"fs" <franc.sutherland@googlemail.com> wrote in message 
news:5cb44ce2-b536-489d-a32d-3f8c257a5831@googlegroups.com...
> On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
>> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
>>
>> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
>> > >> On 31/03/2015 15:56:52, fs wrote:
>> > >> > Hi all,
>> > >> >
>> > >> > I have an Access 2003 database doing a mail merge to Word 2003. It
>> > >> > works f
>> > >> > ine on two Windows XP machines but not with Windows 7.
>> > >> >
>> > >> > On the Windows 7 machines, a Word application opens and the mail 
>> > >> > merge
>> > >> > data is passed (via a txt file) into the .doc file. But the Word 
>> > >> > Window
>> > >> > doesn' t take the focus and the user has to click on it in the 
>> > >> > taskbar
>> > >> > (which does n't happen with the XP machines).
>> > >> >
>> > >> > As well as that, the menus are frozen/inaccessible and the only 
>> > >> > button
>> > >> > that works is the big red x in the top right. When the user clicks 
>> > >> > that
>> > >> > they a re given the Save As option. They can save the file and 
>> > >> > re-open
>> > >> > it
>> > >> > and edi t as normal.
>> > >> >
>> > >> > My question is what is happening when the initial merge is 
>> > >> > happening
>> > >> > and
>> > >> > th e menus are frozen on the Windows 7 machines? Is this a 
>> > >> > permissions
>> > >> > issue to do with Windows 7 and programs activating each other 
>> > >> > using
>> > >> > VBA?
>> > >> >
>> > >> > I'd really appreciate any suggestions. It's been dragging on for 
>> > >> > ages
>> > >> > and
>> > >> > I can't find any information about it anywhere.
>> > >> >
>> > >> > Thanks!
>> > >> >
>> > >>
>> > >> Assuming you are usimg VBA do you have things like
>> > >>
>> > >>     Dim WordApp             As Object       ' Word.Applicaton
>> > >>
>> > >>     Set WordApp = GetObject(, "Word.Application")
>> > >>
>> > >>     WordApp.Visible = True
>> > >>     WordApp.Activate
>> > >>     WordApp.WindowState = 0          'wdWindowStateRestore
>> > >>
>> > >> Phil
>> > >>
>> > >> ---
>> > >> This email has been checked for viruses by Avast antivirus software.
>> > >> http://www.avast.com
>> > >
>> > > Hi Phil,
>> > > Thanks for replying.
>> > >
>> > > I've tried a couple of ways.
>> > >
>> > > The first one was
>> > > ---------------------------------------------------------------------------
>> > > Dim ow As Word.Application
>> > > Dim xDoc As Word.Document
>> > > dim xFilename as string
>> > > dim xDatasource as string
>> > >
>> > > xFilename = "C:\myDoc.doc"
>> > > xDatasource = "C:\myData.csv"
>> > > Set ow = CreateObject("Word.Application")
>> > > Set xDoc = ow.Documents.Open(xFilename)
>> > >
>> > > ow.Documents(x_filename).ActiveWindow.Activate
>> > > ow.Application.WindowState = wdWindowStateMaximize
>> > >
>> > > With Xdoc
>> > >    .MailMerge.OpenDataSource (xDatasource)
>> > >    .MailMerge.Destination = wdSendToNewDocument
>> > >    .MailMerge.Execute
>> > >    .ActiveWindow.Activate
>> > >    .Windows.Application.WindowState = wdWindowStateMaximize
>> > >    .Close
>> > > End With
>> > >
>> > > ow.Visible = True
>> > >
>> > > -----------------------------------------------------------------------------
>> > >
>> > > The second method was more involved but, I thought, bomb-proof way of
>> > > bringing any application into focus.  It involves using Windows API 
>> > > calls
>> > > to read the application's window caption and bring it forward.
>> > >
>> > > Here's the link for it -
>> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
>> > >
>> > > -----------------------------------------------------------------------------
>> > >
>> > > Both of these methods work on the XP machines but neither works on 
>> > > the
>> > > Windows 7 machines.
>> > >
>> > > Any ideas?
>> > >
>> > > Thanks, Franc.
>> > >
>> >
>> > Are you storing the file in the base of the "C" drive? Windows can be 
>> > touchy
>> > about file in that location, try putting it in a folder.
>>
>> Hi Ron,
>> Sorry, no I'm not storing either file in the C drive.  I just put that to 
>> show they were locally stored.  The actual path was a bit long, I thought 
>> it would be easier to just put something like that.  My apologies for 
>> creating the confusion.
>> Thanks, Franc.
>
> Hi Phil,
> I tried that but it didn't change anything I'm afraid.
> I took your idea though and added a couple of new lines
>
> ow.Activate
> ow.Application.WindowState = wdWindowStateMaximize
>
> So the complete code now looks like this
>
> --------------------------------------------------------
> Dim ow As Word.Application
> Dim xDoc As Word.Document
> dim xFilename as string
> dim xDatasource as string
>
> xFilename = "C:\myDoc.doc"
> xDatasource = "C:\myData.csv"
> Set ow = CreateObject("Word.Application")
> Set xDoc = ow.Documents.Open(xFilename)
>
> ow.Documents(x_filename).ActiveWindow.Activate
> ow.Application.WindowState = wdWindowStateMaximize
>
> With Xdoc
>   .MailMerge.OpenDataSource (xDatasource)
>   .MailMerge.Destination = wdSendToNewDocument
>   .MailMerge.Execute
>   .ActiveWindow.Activate
>   .Windows.Application.WindowState = wdWindowStateMaximize
>   .Close
> End With
>
>    ow.Visible = True
>    ow.Activate
>    ow.Application.WindowState = wdWindowStateMaximize
> set ow = Nothing '(this was there already, just forgot to put into the 
> post)
> ---------------------------------------------------------------
>
> With these new lines the problem Windows 7 machine reacts a bit 
> differently.  Now Word opens in the taskbar and flashes and when the user 
> clicks on it the menus are not frozen and they can go ahead with editing. 
> It's progress, but not quite the full solution!
>
> The user has reported that he had the same response of only getting the 
> flashing button in the taskbar when he was using the database on a Windows 
> XP machine but which was XP home edition.  The two XP machines which work 
> as desired are XP Pro machines.  Does this help?
>
> Could the user have changed a Windows setting which stops it happening?
>
>
>
Looking a security features Microsoft added since XP; you may need to add 
the folder to trusted locations.

[toc] | [prev] | [next] | [standalone]

#10587

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-07 07:26 -0700
Message-ID<2ab3da40-66ba-474a-9185-b30066c6420b@googlegroups.com>
In reply to#10574
On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
> "fs" wrote in message 

> > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
> >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
> >>
> >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> >> > >> On 31/03/2015 15:56:52, fs wrote:
> >> > >> > Hi all,
> >> > >> >
> >> > >> > I have an Access 2003 database doing a mail merge to Word 2003. It
> >> > >> > works f
> >> > >> > ine on two Windows XP machines but not with Windows 7.
> >> > >> >
> >> > >> > On the Windows 7 machines, a Word application opens and the mail 
> >> > >> > merge
> >> > >> > data is passed (via a txt file) into the .doc file. But the Word 
> >> > >> > Window
> >> > >> > doesn' t take the focus and the user has to click on it in the 
> >> > >> > taskbar
> >> > >> > (which does n't happen with the XP machines).
> >> > >> >
> >> > >> > As well as that, the menus are frozen/inaccessible and the only 
> >> > >> > button
> >> > >> > that works is the big red x in the top right. When the user clicks 
> >> > >> > that
> >> > >> > they a re given the Save As option. They can save the file and 
> >> > >> > re-open
> >> > >> > it
> >> > >> > and edi t as normal.
> >> > >> >
> >> > >> > My question is what is happening when the initial merge is 
> >> > >> > happening
> >> > >> > and
> >> > >> > th e menus are frozen on the Windows 7 machines? Is this a 
> >> > >> > permissions
> >> > >> > issue to do with Windows 7 and programs activating each other 
> >> > >> > using
> >> > >> > VBA?
> >> > >> >
> >> > >> > I'd really appreciate any suggestions. It's been dragging on for 
> >> > >> > ages
> >> > >> > and
> >> > >> > I can't find any information about it anywhere.
> >> > >> >
> >> > >> > Thanks!
> >> > >> >
> >> > >>
> >> > >> Assuming you are usimg VBA do you have things like
> >> > >>
> >> > >>     Dim WordApp             As Object       ' Word.Applicaton
> >> > >>
> >> > >>     Set WordApp = GetObject(, "Word.Application")
> >> > >>
> >> > >>     WordApp.Visible = True
> >> > >>     WordApp.Activate
> >> > >>     WordApp.WindowState = 0          'wdWindowStateRestore
> >> > >>
> >> > >> Phil
> >> > >>
> >> > >> ---
> >> > >> This email has been checked for viruses by Avast antivirus software.
> >> > >> http://www.avast.com
> >> > >
> >> > > Hi Phil,
> >> > > Thanks for replying.
> >> > >
> >> > > I've tried a couple of ways.
> >> > >
> >> > > The first one was
> >> > > ---------------------------------------------------------------------------
> >> > > Dim ow As Word.Application
> >> > > Dim xDoc As Word.Document
> >> > > dim xFilename as string
> >> > > dim xDatasource as string
> >> > >
> >> > > xFilename = "C:\myDoc.doc"
> >> > > xDatasource = "C:\myData.csv"
> >> > > Set ow = CreateObject("Word.Application")
> >> > > Set xDoc = ow.Documents.Open(xFilename)
> >> > >
> >> > > ow.Documents(x_filename).ActiveWindow.Activate
> >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> > >
> >> > > With Xdoc
> >> > >    .MailMerge.OpenDataSource (xDatasource)
> >> > >    .MailMerge.Destination = wdSendToNewDocument
> >> > >    .MailMerge.Execute
> >> > >    .ActiveWindow.Activate
> >> > >    .Windows.Application.WindowState = wdWindowStateMaximize
> >> > >    .Close
> >> > > End With
> >> > >
> >> > > ow.Visible = True
> >> > >
> >> > > -----------------------------------------------------------------------------
> >> > >
> >> > > The second method was more involved but, I thought, bomb-proof way of
> >> > > bringing any application into focus.  It involves using Windows API 
> >> > > calls
> >> > > to read the application's window caption and bring it forward.
> >> > >
> >> > > Here's the link for it -
> >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> >> > >
> >> > > -----------------------------------------------------------------------------
> >> > >
> >> > > Both of these methods work on the XP machines but neither works on 
> >> > > the
> >> > > Windows 7 machines.
> >> > >
> >> > > Any ideas?
> >> > >
> >> > > Thanks, Franc.
> >> > >
> >> >
> >> > Are you storing the file in the base of the "C" drive? Windows can be 
> >> > touchy
> >> > about file in that location, try putting it in a folder.
> >>
> >> Hi Ron,
> >> Sorry, no I'm not storing either file in the C drive.  I just put that to 
> >> show they were locally stored.  The actual path was a bit long, I thought 
> >> it would be easier to just put something like that.  My apologies for 
> >> creating the confusion.
> >> Thanks, Franc.
> >
> > Hi Phil,
> > I tried that but it didn't change anything I'm afraid.
> > I took your idea though and added a couple of new lines
> >
> > ow.Activate
> > ow.Application.WindowState = wdWindowStateMaximize
> >
> > So the complete code now looks like this
> >
> > --------------------------------------------------------
> > Dim ow As Word.Application
> > Dim xDoc As Word.Document
> > dim xFilename as string
> > dim xDatasource as string
> >
> > xFilename = "C:\myDoc.doc"
> > xDatasource = "C:\myData.csv"
> > Set ow = CreateObject("Word.Application")
> > Set xDoc = ow.Documents.Open(xFilename)
> >
> > ow.Documents(x_filename).ActiveWindow.Activate
> > ow.Application.WindowState = wdWindowStateMaximize
> >
> > With Xdoc
> >   .MailMerge.OpenDataSource (xDatasource)
> >   .MailMerge.Destination = wdSendToNewDocument
> >   .MailMerge.Execute
> >   .ActiveWindow.Activate
> >   .Windows.Application.WindowState = wdWindowStateMaximize
> >   .Close
> > End With
> >
> >    ow.Visible = True
> >    ow.Activate
> >    ow.Application.WindowState = wdWindowStateMaximize
> > set ow = Nothing '(this was there already, just forgot to put into the 
> > post)
> > ---------------------------------------------------------------
> >
> > With these new lines the problem Windows 7 machine reacts a bit 
> > differently.  Now Word opens in the taskbar and flashes and when the user 
> > clicks on it the menus are not frozen and they can go ahead with editing. 
> > It's progress, but not quite the full solution!
> >
> > The user has reported that he had the same response of only getting the 
> > flashing button in the taskbar when he was using the database on a Windows 
> > XP machine but which was XP home edition.  The two XP machines which work 
> > as desired are XP Pro machines.  Does this help?
> >
> > Could the user have changed a Windows setting which stops it happening?
> >
> >
> >
> Looking a security features Microsoft added since XP; you may need to add 
> the folder to trusted locations.

Hi Ron,

I've checked the local intranet settings and this was already in the there:

file://paul-pc

paul-pc is the name of the computer in question which I think adds all local locations to the intranet(?). He doesn't have Office 2007 or higher to set a trusted location that way.  

The front end of the database is in a folder in each user's C drive. I use AutoFEUpdater.

The Word document is accessed via a mapped network drive, Y.  The location of Y is on this user's PC (paul-pc) which is acting as the backend server for the database plus the storage of these shared Word docs.  

I'm not sure what to try next.

[toc] | [prev] | [next] | [standalone]

#10591

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-08 08:12 -0700
Message-ID<58a2098d-ca1c-46c3-bdd0-0f8af9e54824@googlegroups.com>
In reply to#10587
On Tuesday, 7 April 2015 15:26:06 UTC+1, fs  wrote:
> On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
> > "fs" wrote in message 
> 
> > > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
> > >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
> > >>
> > >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> > >> > >> On 31/03/2015 15:56:52, fs wrote:
> > >> > >> > Hi all,
> > >> > >> >
> > >> > >> > I have an Access 2003 database doing a mail merge to Word 2003. It
> > >> > >> > works f
> > >> > >> > ine on two Windows XP machines but not with Windows 7.
> > >> > >> >
> > >> > >> > On the Windows 7 machines, a Word application opens and the mail 
> > >> > >> > merge
> > >> > >> > data is passed (via a txt file) into the .doc file. But the Word 
> > >> > >> > Window
> > >> > >> > doesn' t take the focus and the user has to click on it in the 
> > >> > >> > taskbar
> > >> > >> > (which does n't happen with the XP machines).
> > >> > >> >
> > >> > >> > As well as that, the menus are frozen/inaccessible and the only 
> > >> > >> > button
> > >> > >> > that works is the big red x in the top right. When the user clicks 
> > >> > >> > that
> > >> > >> > they a re given the Save As option. They can save the file and 
> > >> > >> > re-open
> > >> > >> > it
> > >> > >> > and edi t as normal.
> > >> > >> >
> > >> > >> > My question is what is happening when the initial merge is 
> > >> > >> > happening
> > >> > >> > and
> > >> > >> > th e menus are frozen on the Windows 7 machines? Is this a 
> > >> > >> > permissions
> > >> > >> > issue to do with Windows 7 and programs activating each other 
> > >> > >> > using
> > >> > >> > VBA?
> > >> > >> >
> > >> > >> > I'd really appreciate any suggestions. It's been dragging on for 
> > >> > >> > ages
> > >> > >> > and
> > >> > >> > I can't find any information about it anywhere.
> > >> > >> >
> > >> > >> > Thanks!
> > >> > >> >
> > >> > >>
> > >> > >> Assuming you are usimg VBA do you have things like
> > >> > >>
> > >> > >>     Dim WordApp             As Object       ' Word.Applicaton
> > >> > >>
> > >> > >>     Set WordApp = GetObject(, "Word.Application")
> > >> > >>
> > >> > >>     WordApp.Visible = True
> > >> > >>     WordApp.Activate
> > >> > >>     WordApp.WindowState = 0          'wdWindowStateRestore
> > >> > >>
> > >> > >> Phil
> > >> > >>
> > >> > >> ---
> > >> > >> This email has been checked for viruses by Avast antivirus software.
> > >> > >> http://www.avast.com
> > >> > >
> > >> > > Hi Phil,
> > >> > > Thanks for replying.
> > >> > >
> > >> > > I've tried a couple of ways.
> > >> > >
> > >> > > The first one was
> > >> > > ---------------------------------------------------------------------------
> > >> > > Dim ow As Word.Application
> > >> > > Dim xDoc As Word.Document
> > >> > > dim xFilename as string
> > >> > > dim xDatasource as string
> > >> > >
> > >> > > xFilename = "C:\myDoc.doc"
> > >> > > xDatasource = "C:\myData.csv"
> > >> > > Set ow = CreateObject("Word.Application")
> > >> > > Set xDoc = ow.Documents.Open(xFilename)
> > >> > >
> > >> > > ow.Documents(x_filename).ActiveWindow.Activate
> > >> > > ow.Application.WindowState = wdWindowStateMaximize
> > >> > >
> > >> > > With Xdoc
> > >> > >    .MailMerge.OpenDataSource (xDatasource)
> > >> > >    .MailMerge.Destination = wdSendToNewDocument
> > >> > >    .MailMerge.Execute
> > >> > >    .ActiveWindow.Activate
> > >> > >    .Windows.Application.WindowState = wdWindowStateMaximize
> > >> > >    .Close
> > >> > > End With
> > >> > >
> > >> > > ow.Visible = True
> > >> > >
> > >> > > -----------------------------------------------------------------------------
> > >> > >
> > >> > > The second method was more involved but, I thought, bomb-proof way of
> > >> > > bringing any application into focus.  It involves using Windows API 
> > >> > > calls
> > >> > > to read the application's window caption and bring it forward.
> > >> > >
> > >> > > Here's the link for it -
> > >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> > >> > >
> > >> > > -----------------------------------------------------------------------------
> > >> > >
> > >> > > Both of these methods work on the XP machines but neither works on 
> > >> > > the
> > >> > > Windows 7 machines.
> > >> > >
> > >> > > Any ideas?
> > >> > >
> > >> > > Thanks, Franc.
> > >> > >
> > >> >
> > >> > Are you storing the file in the base of the "C" drive? Windows can be 
> > >> > touchy
> > >> > about file in that location, try putting it in a folder.
> > >>
> > >> Hi Ron,
> > >> Sorry, no I'm not storing either file in the C drive.  I just put that to 
> > >> show they were locally stored.  The actual path was a bit long, I thought 
> > >> it would be easier to just put something like that.  My apologies for 
> > >> creating the confusion.
> > >> Thanks, Franc.
> > >
> > > Hi Phil,
> > > I tried that but it didn't change anything I'm afraid.
> > > I took your idea though and added a couple of new lines
> > >
> > > ow.Activate
> > > ow.Application.WindowState = wdWindowStateMaximize
> > >
> > > So the complete code now looks like this
> > >
> > > --------------------------------------------------------
> > > Dim ow As Word.Application
> > > Dim xDoc As Word.Document
> > > dim xFilename as string
> > > dim xDatasource as string
> > >
> > > xFilename = "C:\myDoc.doc"
> > > xDatasource = "C:\myData.csv"
> > > Set ow = CreateObject("Word.Application")
> > > Set xDoc = ow.Documents.Open(xFilename)
> > >
> > > ow.Documents(x_filename).ActiveWindow.Activate
> > > ow.Application.WindowState = wdWindowStateMaximize
> > >
> > > With Xdoc
> > >   .MailMerge.OpenDataSource (xDatasource)
> > >   .MailMerge.Destination = wdSendToNewDocument
> > >   .MailMerge.Execute
> > >   .ActiveWindow.Activate
> > >   .Windows.Application.WindowState = wdWindowStateMaximize
> > >   .Close
> > > End With
> > >
> > >    ow.Visible = True
> > >    ow.Activate
> > >    ow.Application.WindowState = wdWindowStateMaximize
> > > set ow = Nothing '(this was there already, just forgot to put into the 
> > > post)
> > > ---------------------------------------------------------------
> > >
> > > With these new lines the problem Windows 7 machine reacts a bit 
> > > differently.  Now Word opens in the taskbar and flashes and when the user 
> > > clicks on it the menus are not frozen and they can go ahead with editing. 
> > > It's progress, but not quite the full solution!
> > >
> > > The user has reported that he had the same response of only getting the 
> > > flashing button in the taskbar when he was using the database on a Windows 
> > > XP machine but which was XP home edition.  The two XP machines which work 
> > > as desired are XP Pro machines.  Does this help?
> > >
> > > Could the user have changed a Windows setting which stops it happening?
> > >
> > >
> > >
> > Looking a security features Microsoft added since XP; you may need to add 
> > the folder to trusted locations.
> 
> Hi Ron,
> 
> I've checked the local intranet settings and this was already in the there:
> 
> file://paul-pc
> 
> paul-pc is the name of the computer in question which I think adds all local locations to the intranet(?). He doesn't have Office 2007 or higher to set a trusted location that way.  
> 
> The front end of the database is in a folder in each user's C drive. I use AutoFEUpdater.
> 
> The Word document is accessed via a mapped network drive, Y.  The location of Y is on this user's PC (paul-pc) which is acting as the backend server for the database plus the storage of these shared Word docs.  
> 
> I'm not sure what to try next.

I've made sure the Windows 7 network type was 'Home'.
The Windows 7 PC is in a Homegroup and Documents are shared.

I think it might be more to do with the user access control part of Windows 7 rather than the network side of things.

Any ideas?

[toc] | [prev] | [next] | [standalone]

#10594

From"Ron Paii" <None@none.com>
Date2015-04-08 15:59 -0500
Message-ID<mg44pj$qi7$1@dont-email.me>
In reply to#10591

"fs" <franc.sutherland@googlemail.com> wrote in message 
news:58a2098d-ca1c-46c3-bdd0-0f8af9e54824@googlegroups.com...
> On Tuesday, 7 April 2015 15:26:06 UTC+1, fs  wrote:
>> On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
>> > "fs" wrote in message
>>
>> > > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
>> > >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
>> > >>
>> > >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
>> > >> > >> On 31/03/2015 15:56:52, fs wrote:
>> > >> > >> > Hi all,
>> > >> > >> >
>> > >> > >> > I have an Access 2003 database doing a mail merge to Word 
>> > >> > >> > 2003. It
>> > >> > >> > works f
>> > >> > >> > ine on two Windows XP machines but not with Windows 7.
>> > >> > >> >
>> > >> > >> > On the Windows 7 machines, a Word application opens and the 
>> > >> > >> > mail
>> > >> > >> > merge
>> > >> > >> > data is passed (via a txt file) into the .doc file. But the 
>> > >> > >> > Word
>> > >> > >> > Window
>> > >> > >> > doesn' t take the focus and the user has to click on it in 
>> > >> > >> > the
>> > >> > >> > taskbar
>> > >> > >> > (which does n't happen with the XP machines).
>> > >> > >> >
>> > >> > >> > As well as that, the menus are frozen/inaccessible and the 
>> > >> > >> > only
>> > >> > >> > button
>> > >> > >> > that works is the big red x in the top right. When the user 
>> > >> > >> > clicks
>> > >> > >> > that
>> > >> > >> > they a re given the Save As option. They can save the file 
>> > >> > >> > and
>> > >> > >> > re-open
>> > >> > >> > it
>> > >> > >> > and edi t as normal.
>> > >> > >> >
>> > >> > >> > My question is what is happening when the initial merge is
>> > >> > >> > happening
>> > >> > >> > and
>> > >> > >> > th e menus are frozen on the Windows 7 machines? Is this a
>> > >> > >> > permissions
>> > >> > >> > issue to do with Windows 7 and programs activating each other
>> > >> > >> > using
>> > >> > >> > VBA?
>> > >> > >> >
>> > >> > >> > I'd really appreciate any suggestions. It's been dragging on 
>> > >> > >> > for
>> > >> > >> > ages
>> > >> > >> > and
>> > >> > >> > I can't find any information about it anywhere.
>> > >> > >> >
>> > >> > >> > Thanks!
>> > >> > >> >
>> > >> > >>
>> > >> > >> Assuming you are usimg VBA do you have things like
>> > >> > >>
>> > >> > >>     Dim WordApp             As Object       ' Word.Applicaton
>> > >> > >>
>> > >> > >>     Set WordApp = GetObject(, "Word.Application")
>> > >> > >>
>> > >> > >>     WordApp.Visible = True
>> > >> > >>     WordApp.Activate
>> > >> > >>     WordApp.WindowState = 0          'wdWindowStateRestore
>> > >> > >>
>> > >> > >> Phil
>> > >> > >>
>> > >> > >> ---
>> > >> > >> This email has been checked for viruses by Avast antivirus 
>> > >> > >> software.
>> > >> > >> http://www.avast.com
>> > >> > >
>> > >> > > Hi Phil,
>> > >> > > Thanks for replying.
>> > >> > >
>> > >> > > I've tried a couple of ways.
>> > >> > >
>> > >> > > The first one was
>> > >> > > ---------------------------------------------------------------------------
>> > >> > > Dim ow As Word.Application
>> > >> > > Dim xDoc As Word.Document
>> > >> > > dim xFilename as string
>> > >> > > dim xDatasource as string
>> > >> > >
>> > >> > > xFilename = "C:\myDoc.doc"
>> > >> > > xDatasource = "C:\myData.csv"
>> > >> > > Set ow = CreateObject("Word.Application")
>> > >> > > Set xDoc = ow.Documents.Open(xFilename)
>> > >> > >
>> > >> > > ow.Documents(x_filename).ActiveWindow.Activate
>> > >> > > ow.Application.WindowState = wdWindowStateMaximize
>> > >> > >
>> > >> > > With Xdoc
>> > >> > >    .MailMerge.OpenDataSource (xDatasource)
>> > >> > >    .MailMerge.Destination = wdSendToNewDocument
>> > >> > >    .MailMerge.Execute
>> > >> > >    .ActiveWindow.Activate
>> > >> > >    .Windows.Application.WindowState = wdWindowStateMaximize
>> > >> > >    .Close
>> > >> > > End With
>> > >> > >
>> > >> > > ow.Visible = True
>> > >> > >
>> > >> > > -----------------------------------------------------------------------------
>> > >> > >
>> > >> > > The second method was more involved but, I thought, bomb-proof 
>> > >> > > way of
>> > >> > > bringing any application into focus.  It involves using Windows 
>> > >> > > API
>> > >> > > calls
>> > >> > > to read the application's window caption and bring it forward.
>> > >> > >
>> > >> > > Here's the link for it -
>> > >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
>> > >> > >
>> > >> > > -----------------------------------------------------------------------------
>> > >> > >
>> > >> > > Both of these methods work on the XP machines but neither works 
>> > >> > > on
>> > >> > > the
>> > >> > > Windows 7 machines.
>> > >> > >
>> > >> > > Any ideas?
>> > >> > >
>> > >> > > Thanks, Franc.
>> > >> > >
>> > >> >
>> > >> > Are you storing the file in the base of the "C" drive? Windows can 
>> > >> > be
>> > >> > touchy
>> > >> > about file in that location, try putting it in a folder.
>> > >>
>> > >> Hi Ron,
>> > >> Sorry, no I'm not storing either file in the C drive.  I just put 
>> > >> that to
>> > >> show they were locally stored.  The actual path was a bit long, I 
>> > >> thought
>> > >> it would be easier to just put something like that.  My apologies 
>> > >> for
>> > >> creating the confusion.
>> > >> Thanks, Franc.
>> > >
>> > > Hi Phil,
>> > > I tried that but it didn't change anything I'm afraid.
>> > > I took your idea though and added a couple of new lines
>> > >
>> > > ow.Activate
>> > > ow.Application.WindowState = wdWindowStateMaximize
>> > >
>> > > So the complete code now looks like this
>> > >
>> > > --------------------------------------------------------
>> > > Dim ow As Word.Application
>> > > Dim xDoc As Word.Document
>> > > dim xFilename as string
>> > > dim xDatasource as string
>> > >
>> > > xFilename = "C:\myDoc.doc"
>> > > xDatasource = "C:\myData.csv"
>> > > Set ow = CreateObject("Word.Application")
>> > > Set xDoc = ow.Documents.Open(xFilename)
>> > >
>> > > ow.Documents(x_filename).ActiveWindow.Activate
>> > > ow.Application.WindowState = wdWindowStateMaximize
>> > >
>> > > With Xdoc
>> > >   .MailMerge.OpenDataSource (xDatasource)
>> > >   .MailMerge.Destination = wdSendToNewDocument
>> > >   .MailMerge.Execute
>> > >   .ActiveWindow.Activate
>> > >   .Windows.Application.WindowState = wdWindowStateMaximize
>> > >   .Close
>> > > End With
>> > >
>> > >    ow.Visible = True
>> > >    ow.Activate
>> > >    ow.Application.WindowState = wdWindowStateMaximize
>> > > set ow = Nothing '(this was there already, just forgot to put into 
>> > > the
>> > > post)
>> > > ---------------------------------------------------------------
>> > >
>> > > With these new lines the problem Windows 7 machine reacts a bit
>> > > differently.  Now Word opens in the taskbar and flashes and when the 
>> > > user
>> > > clicks on it the menus are not frozen and they can go ahead with 
>> > > editing.
>> > > It's progress, but not quite the full solution!
>> > >
>> > > The user has reported that he had the same response of only getting 
>> > > the
>> > > flashing button in the taskbar when he was using the database on a 
>> > > Windows
>> > > XP machine but which was XP home edition.  The two XP machines which 
>> > > work
>> > > as desired are XP Pro machines.  Does this help?
>> > >
>> > > Could the user have changed a Windows setting which stops it 
>> > > happening?
>> > >
>> > >
>> > >
>> > Looking a security features Microsoft added since XP; you may need to 
>> > add
>> > the folder to trusted locations.
>>
>> Hi Ron,
>>
>> I've checked the local intranet settings and this was already in the 
>> there:
>>
>> file://paul-pc
>>
>> paul-pc is the name of the computer in question which I think adds all 
>> local locations to the intranet(?). He doesn't have Office 2007 or higher 
>> to set a trusted location that way.
>>
>> The front end of the database is in a folder in each user's C drive. I 
>> use AutoFEUpdater.
>>
>> The Word document is accessed via a mapped network drive, Y.  The 
>> location of Y is on this user's PC (paul-pc) which is acting as the 
>> backend server for the database plus the storage of these shared Word 
>> docs.
>>
>> I'm not sure what to try next.
>
> I've made sure the Windows 7 network type was 'Home'.
> The Windows 7 PC is in a Homegroup and Documents are shared.
>
> I think it might be more to do with the user access control part of 
> Windows 7 rather than the network side of things.
>
> Any ideas?

Build a test environment by move everything into a local folder that is a 
trusted location. If the problem continues it is not a security issue. 
Otherwise move the Word file into the product folder and test again. Keep 
move parts of the app into product folders until the problem returns.

[toc] | [prev] | [next] | [standalone]

#10597

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-09 02:54 -0700
Message-ID<3df5a995-062e-4c97-918e-3133a03f8c71@googlegroups.com>
In reply to#10594
On Wednesday, 8 April 2015 21:59:31 UTC+1, Ron Paii  wrote:

> > On Tuesday, 7 April 2015 15:26:06 UTC+1, fs  wrote:
> >> On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
> >> > "fs" wrote in message
> >>
> >> > > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
> >> > >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
> >> > >>
> >> > >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> >> > >> > >> On 31/03/2015 15:56:52, fs wrote:
> >> > >> > >> > Hi all,
> >> > >> > >> >
> >> > >> > >> > I have an Access 2003 database doing a mail merge to Word 
> >> > >> > >> > 2003. It
> >> > >> > >> > works f
> >> > >> > >> > ine on two Windows XP machines but not with Windows 7.
> >> > >> > >> >
> >> > >> > >> > On the Windows 7 machines, a Word application opens and the 
> >> > >> > >> > mail
> >> > >> > >> > merge
> >> > >> > >> > data is passed (via a txt file) into the .doc file. But the 
> >> > >> > >> > Word
> >> > >> > >> > Window
> >> > >> > >> > doesn' t take the focus and the user has to click on it in 
> >> > >> > >> > the
> >> > >> > >> > taskbar
> >> > >> > >> > (which does n't happen with the XP machines).
> >> > >> > >> >
> >> > >> > >> > As well as that, the menus are frozen/inaccessible and the 
> >> > >> > >> > only
> >> > >> > >> > button
> >> > >> > >> > that works is the big red x in the top right. When the user 
> >> > >> > >> > clicks
> >> > >> > >> > that
> >> > >> > >> > they a re given the Save As option. They can save the file 
> >> > >> > >> > and
> >> > >> > >> > re-open
> >> > >> > >> > it
> >> > >> > >> > and edi t as normal.
> >> > >> > >> >
> >> > >> > >> > My question is what is happening when the initial merge is
> >> > >> > >> > happening
> >> > >> > >> > and
> >> > >> > >> > th e menus are frozen on the Windows 7 machines? Is this a
> >> > >> > >> > permissions
> >> > >> > >> > issue to do with Windows 7 and programs activating each other
> >> > >> > >> > using
> >> > >> > >> > VBA?
> >> > >> > >> >
> >> > >> > >> > I'd really appreciate any suggestions. It's been dragging on 
> >> > >> > >> > for
> >> > >> > >> > ages
> >> > >> > >> > and
> >> > >> > >> > I can't find any information about it anywhere.
> >> > >> > >> >
> >> > >> > >> > Thanks!
> >> > >> > >> >
> >> > >> > >>
> >> > >> > >> Assuming you are usimg VBA do you have things like
> >> > >> > >>
> >> > >> > >>     Dim WordApp             As Object       ' Word.Applicaton
> >> > >> > >>
> >> > >> > >>     Set WordApp = GetObject(, "Word.Application")
> >> > >> > >>
> >> > >> > >>     WordApp.Visible = True
> >> > >> > >>     WordApp.Activate
> >> > >> > >>     WordApp.WindowState = 0          'wdWindowStateRestore
> >> > >> > >>
> >> > >> > >> Phil
> >> > >> > >>
> >> > >> > >> ---
> >> > >> > >> This email has been checked for viruses by Avast antivirus 
> >> > >> > >> software.
> >> > >> > >> http://www.avast.com
> >> > >> > >
> >> > >> > > Hi Phil,
> >> > >> > > Thanks for replying.
> >> > >> > >
> >> > >> > > I've tried a couple of ways.
> >> > >> > >
> >> > >> > > The first one was
> >> > >> > > ---------------------------------------------------------------------------
> >> > >> > > Dim ow As Word.Application
> >> > >> > > Dim xDoc As Word.Document
> >> > >> > > dim xFilename as string
> >> > >> > > dim xDatasource as string
> >> > >> > >
> >> > >> > > xFilename = "C:\myDoc.doc"
> >> > >> > > xDatasource = "C:\myData.csv"
> >> > >> > > Set ow = CreateObject("Word.Application")
> >> > >> > > Set xDoc = ow.Documents.Open(xFilename)
> >> > >> > >
> >> > >> > > ow.Documents(x_filename).ActiveWindow.Activate
> >> > >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> > >> > >
> >> > >> > > With Xdoc
> >> > >> > >    .MailMerge.OpenDataSource (xDatasource)
> >> > >> > >    .MailMerge.Destination = wdSendToNewDocument
> >> > >> > >    .MailMerge.Execute
> >> > >> > >    .ActiveWindow.Activate
> >> > >> > >    .Windows.Application.WindowState = wdWindowStateMaximize
> >> > >> > >    .Close
> >> > >> > > End With
> >> > >> > >
> >> > >> > > ow.Visible = True
> >> > >> > >
> >> > >> > > -----------------------------------------------------------------------------
> >> > >> > >
> >> > >> > > The second method was more involved but, I thought, bomb-proof 
> >> > >> > > way of
> >> > >> > > bringing any application into focus.  It involves using Windows 
> >> > >> > > API
> >> > >> > > calls
> >> > >> > > to read the application's window caption and bring it forward.
> >> > >> > >
> >> > >> > > Here's the link for it -
> >> > >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> >> > >> > >
> >> > >> > > -----------------------------------------------------------------------------
> >> > >> > >
> >> > >> > > Both of these methods work on the XP machines but neither works 
> >> > >> > > on
> >> > >> > > the
> >> > >> > > Windows 7 machines.
> >> > >> > >
> >> > >> > > Any ideas?
> >> > >> > >
> >> > >> > > Thanks, Franc.
> >> > >> > >
> >> > >> >
> >> > >> > Are you storing the file in the base of the "C" drive? Windows can 
> >> > >> > be
> >> > >> > touchy
> >> > >> > about file in that location, try putting it in a folder.
> >> > >>
> >> > >> Hi Ron,
> >> > >> Sorry, no I'm not storing either file in the C drive.  I just put 
> >> > >> that to
> >> > >> show they were locally stored.  The actual path was a bit long, I 
> >> > >> thought
> >> > >> it would be easier to just put something like that.  My apologies 
> >> > >> for
> >> > >> creating the confusion.
> >> > >> Thanks, Franc.
> >> > >
> >> > > Hi Phil,
> >> > > I tried that but it didn't change anything I'm afraid.
> >> > > I took your idea though and added a couple of new lines
> >> > >
> >> > > ow.Activate
> >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> > >
> >> > > So the complete code now looks like this
> >> > >
> >> > > --------------------------------------------------------
> >> > > Dim ow As Word.Application
> >> > > Dim xDoc As Word.Document
> >> > > dim xFilename as string
> >> > > dim xDatasource as string
> >> > >
> >> > > xFilename = "C:\myDoc.doc"
> >> > > xDatasource = "C:\myData.csv"
> >> > > Set ow = CreateObject("Word.Application")
> >> > > Set xDoc = ow.Documents.Open(xFilename)
> >> > >
> >> > > ow.Documents(x_filename).ActiveWindow.Activate
> >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> > >
> >> > > With Xdoc
> >> > >   .MailMerge.OpenDataSource (xDatasource)
> >> > >   .MailMerge.Destination = wdSendToNewDocument
> >> > >   .MailMerge.Execute
> >> > >   .ActiveWindow.Activate
> >> > >   .Windows.Application.WindowState = wdWindowStateMaximize
> >> > >   .Close
> >> > > End With
> >> > >
> >> > >    ow.Visible = True
> >> > >    ow.Activate
> >> > >    ow.Application.WindowState = wdWindowStateMaximize
> >> > > set ow = Nothing '(this was there already, just forgot to put into 
> >> > > the
> >> > > post)
> >> > > ---------------------------------------------------------------
> >> > >
> >> > > With these new lines the problem Windows 7 machine reacts a bit
> >> > > differently.  Now Word opens in the taskbar and flashes and when the 
> >> > > user
> >> > > clicks on it the menus are not frozen and they can go ahead with 
> >> > > editing.
> >> > > It's progress, but not quite the full solution!
> >> > >
> >> > > The user has reported that he had the same response of only getting 
> >> > > the
> >> > > flashing button in the taskbar when he was using the database on a 
> >> > > Windows
> >> > > XP machine but which was XP home edition.  The two XP machines which 
> >> > > work
> >> > > as desired are XP Pro machines.  Does this help?
> >> > >
> >> > > Could the user have changed a Windows setting which stops it 
> >> > > happening?
> >> > >
> >> > >
> >> > >
> >> > Looking a security features Microsoft added since XP; you may need to 
> >> > add
> >> > the folder to trusted locations.
> >>
> >> Hi Ron,
> >>
> >> I've checked the local intranet settings and this was already in the 
> >> there:
> >>
> >> file://paul-pc
> >>
> >> paul-pc is the name of the computer in question which I think adds all 
> >> local locations to the intranet(?). He doesn't have Office 2007 or higher 
> >> to set a trusted location that way.
> >>
> >> The front end of the database is in a folder in each user's C drive. I 
> >> use AutoFEUpdater.
> >>
> >> The Word document is accessed via a mapped network drive, Y.  The 
> >> location of Y is on this user's PC (paul-pc) which is acting as the 
> >> backend server for the database plus the storage of these shared Word 
> >> docs.
> >>
> >> I'm not sure what to try next.
> >
> > I've made sure the Windows 7 network type was 'Home'.
> > The Windows 7 PC is in a Homegroup and Documents are shared.
> >
> > I think it might be more to do with the user access control part of 
> > Windows 7 rather than the network side of things.
> >
> > Any ideas?
> 
> Build a test environment by move everything into a local folder that is a 
> trusted location. If the problem continues it is not a security issue. 
> Otherwise move the Word file into the product folder and test again. Keep 
> move parts of the app into product folders until the problem returns.

Hi Ron, how do I make a local folder a trusted location in Office 2003?
All the files on the computer are part of the intranet in Internet Options, as per the 'file://paul-pc' site listing.
I have tried moving the mdb and the doc file to a new folder in the user's C:\Documents folder but with the same outcome.

[toc] | [prev] | [next] | [standalone]

#10600

From"Ron Paii" <None@none.com>
Date2015-04-09 16:02 -0500
Message-ID<mg6pbo$rs2$1@dont-email.me>
In reply to#10597

"fs" <franc.sutherland@googlemail.com> wrote in message 
news:3df5a995-062e-4c97-918e-3133a03f8c71@googlegroups.com...
> On Wednesday, 8 April 2015 21:59:31 UTC+1, Ron Paii  wrote:
>
>> > On Tuesday, 7 April 2015 15:26:06 UTC+1, fs  wrote:
>> >> On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
>> >> > "fs" wrote in message
>> >>
>> >> > > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
>> >> > >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
>> >> > >>
>> >> > >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
>> >> > >> > >> On 31/03/2015 15:56:52, fs wrote:
>> >> > >> > >> > Hi all,
>> >> > >> > >> >
>> >> > >> > >> > I have an Access 2003 database doing a mail merge to Word
>> >> > >> > >> > 2003. It
>> >> > >> > >> > works f
>> >> > >> > >> > ine on two Windows XP machines but not with Windows 7.
>> >> > >> > >> >
>> >> > >> > >> > On the Windows 7 machines, a Word application opens and 
>> >> > >> > >> > the
>> >> > >> > >> > mail
>> >> > >> > >> > merge
>> >> > >> > >> > data is passed (via a txt file) into the .doc file. But 
>> >> > >> > >> > the
>> >> > >> > >> > Word
>> >> > >> > >> > Window
>> >> > >> > >> > doesn' t take the focus and the user has to click on it in
>> >> > >> > >> > the
>> >> > >> > >> > taskbar
>> >> > >> > >> > (which does n't happen with the XP machines).
>> >> > >> > >> >
>> >> > >> > >> > As well as that, the menus are frozen/inaccessible and the
>> >> > >> > >> > only
>> >> > >> > >> > button
>> >> > >> > >> > that works is the big red x in the top right. When the 
>> >> > >> > >> > user
>> >> > >> > >> > clicks
>> >> > >> > >> > that
>> >> > >> > >> > they a re given the Save As option. They can save the file
>> >> > >> > >> > and
>> >> > >> > >> > re-open
>> >> > >> > >> > it
>> >> > >> > >> > and edi t as normal.
>> >> > >> > >> >
>> >> > >> > >> > My question is what is happening when the initial merge is
>> >> > >> > >> > happening
>> >> > >> > >> > and
>> >> > >> > >> > th e menus are frozen on the Windows 7 machines? Is this a
>> >> > >> > >> > permissions
>> >> > >> > >> > issue to do with Windows 7 and programs activating each 
>> >> > >> > >> > other
>> >> > >> > >> > using
>> >> > >> > >> > VBA?
>> >> > >> > >> >
>> >> > >> > >> > I'd really appreciate any suggestions. It's been dragging 
>> >> > >> > >> > on
>> >> > >> > >> > for
>> >> > >> > >> > ages
>> >> > >> > >> > and
>> >> > >> > >> > I can't find any information about it anywhere.
>> >> > >> > >> >
>> >> > >> > >> > Thanks!
>> >> > >> > >> >
>> >> > >> > >>
>> >> > >> > >> Assuming you are usimg VBA do you have things like
>> >> > >> > >>
>> >> > >> > >>     Dim WordApp             As Object       ' 
>> >> > >> > >> Word.Applicaton
>> >> > >> > >>
>> >> > >> > >>     Set WordApp = GetObject(, "Word.Application")
>> >> > >> > >>
>> >> > >> > >>     WordApp.Visible = True
>> >> > >> > >>     WordApp.Activate
>> >> > >> > >>     WordApp.WindowState = 0          'wdWindowStateRestore
>> >> > >> > >>
>> >> > >> > >> Phil
>> >> > >> > >>
>> >> > >> > >> ---
>> >> > >> > >> This email has been checked for viruses by Avast antivirus
>> >> > >> > >> software.
>> >> > >> > >> http://www.avast.com
>> >> > >> > >
>> >> > >> > > Hi Phil,
>> >> > >> > > Thanks for replying.
>> >> > >> > >
>> >> > >> > > I've tried a couple of ways.
>> >> > >> > >
>> >> > >> > > The first one was
>> >> > >> > > ---------------------------------------------------------------------------
>> >> > >> > > Dim ow As Word.Application
>> >> > >> > > Dim xDoc As Word.Document
>> >> > >> > > dim xFilename as string
>> >> > >> > > dim xDatasource as string
>> >> > >> > >
>> >> > >> > > xFilename = "C:\myDoc.doc"
>> >> > >> > > xDatasource = "C:\myData.csv"
>> >> > >> > > Set ow = CreateObject("Word.Application")
>> >> > >> > > Set xDoc = ow.Documents.Open(xFilename)
>> >> > >> > >
>> >> > >> > > ow.Documents(x_filename).ActiveWindow.Activate
>> >> > >> > > ow.Application.WindowState = wdWindowStateMaximize
>> >> > >> > >
>> >> > >> > > With Xdoc
>> >> > >> > >    .MailMerge.OpenDataSource (xDatasource)
>> >> > >> > >    .MailMerge.Destination = wdSendToNewDocument
>> >> > >> > >    .MailMerge.Execute
>> >> > >> > >    .ActiveWindow.Activate
>> >> > >> > >    .Windows.Application.WindowState = wdWindowStateMaximize
>> >> > >> > >    .Close
>> >> > >> > > End With
>> >> > >> > >
>> >> > >> > > ow.Visible = True
>> >> > >> > >
>> >> > >> > > -----------------------------------------------------------------------------
>> >> > >> > >
>> >> > >> > > The second method was more involved but, I thought, 
>> >> > >> > > bomb-proof
>> >> > >> > > way of
>> >> > >> > > bringing any application into focus.  It involves using 
>> >> > >> > > Windows
>> >> > >> > > API
>> >> > >> > > calls
>> >> > >> > > to read the application's window caption and bring it 
>> >> > >> > > forward.
>> >> > >> > >
>> >> > >> > > Here's the link for it -
>> >> > >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
>> >> > >> > >
>> >> > >> > > -----------------------------------------------------------------------------
>> >> > >> > >
>> >> > >> > > Both of these methods work on the XP machines but neither 
>> >> > >> > > works
>> >> > >> > > on
>> >> > >> > > the
>> >> > >> > > Windows 7 machines.
>> >> > >> > >
>> >> > >> > > Any ideas?
>> >> > >> > >
>> >> > >> > > Thanks, Franc.
>> >> > >> > >
>> >> > >> >
>> >> > >> > Are you storing the file in the base of the "C" drive? Windows 
>> >> > >> > can
>> >> > >> > be
>> >> > >> > touchy
>> >> > >> > about file in that location, try putting it in a folder.
>> >> > >>
>> >> > >> Hi Ron,
>> >> > >> Sorry, no I'm not storing either file in the C drive.  I just put
>> >> > >> that to
>> >> > >> show they were locally stored.  The actual path was a bit long, I
>> >> > >> thought
>> >> > >> it would be easier to just put something like that.  My apologies
>> >> > >> for
>> >> > >> creating the confusion.
>> >> > >> Thanks, Franc.
>> >> > >
>> >> > > Hi Phil,
>> >> > > I tried that but it didn't change anything I'm afraid.
>> >> > > I took your idea though and added a couple of new lines
>> >> > >
>> >> > > ow.Activate
>> >> > > ow.Application.WindowState = wdWindowStateMaximize
>> >> > >
>> >> > > So the complete code now looks like this
>> >> > >
>> >> > > --------------------------------------------------------
>> >> > > Dim ow As Word.Application
>> >> > > Dim xDoc As Word.Document
>> >> > > dim xFilename as string
>> >> > > dim xDatasource as string
>> >> > >
>> >> > > xFilename = "C:\myDoc.doc"
>> >> > > xDatasource = "C:\myData.csv"
>> >> > > Set ow = CreateObject("Word.Application")
>> >> > > Set xDoc = ow.Documents.Open(xFilename)
>> >> > >
>> >> > > ow.Documents(x_filename).ActiveWindow.Activate
>> >> > > ow.Application.WindowState = wdWindowStateMaximize
>> >> > >
>> >> > > With Xdoc
>> >> > >   .MailMerge.OpenDataSource (xDatasource)
>> >> > >   .MailMerge.Destination = wdSendToNewDocument
>> >> > >   .MailMerge.Execute
>> >> > >   .ActiveWindow.Activate
>> >> > >   .Windows.Application.WindowState = wdWindowStateMaximize
>> >> > >   .Close
>> >> > > End With
>> >> > >
>> >> > >    ow.Visible = True
>> >> > >    ow.Activate
>> >> > >    ow.Application.WindowState = wdWindowStateMaximize
>> >> > > set ow = Nothing '(this was there already, just forgot to put into
>> >> > > the
>> >> > > post)
>> >> > > ---------------------------------------------------------------
>> >> > >
>> >> > > With these new lines the problem Windows 7 machine reacts a bit
>> >> > > differently.  Now Word opens in the taskbar and flashes and when 
>> >> > > the
>> >> > > user
>> >> > > clicks on it the menus are not frozen and they can go ahead with
>> >> > > editing.
>> >> > > It's progress, but not quite the full solution!
>> >> > >
>> >> > > The user has reported that he had the same response of only 
>> >> > > getting
>> >> > > the
>> >> > > flashing button in the taskbar when he was using the database on a
>> >> > > Windows
>> >> > > XP machine but which was XP home edition.  The two XP machines 
>> >> > > which
>> >> > > work
>> >> > > as desired are XP Pro machines.  Does this help?
>> >> > >
>> >> > > Could the user have changed a Windows setting which stops it
>> >> > > happening?
>> >> > >
>> >> > >
>> >> > >
>> >> > Looking a security features Microsoft added since XP; you may need 
>> >> > to
>> >> > add
>> >> > the folder to trusted locations.
>> >>
>> >> Hi Ron,
>> >>
>> >> I've checked the local intranet settings and this was already in the
>> >> there:
>> >>
>> >> file://paul-pc
>> >>
>> >> paul-pc is the name of the computer in question which I think adds all
>> >> local locations to the intranet(?). He doesn't have Office 2007 or 
>> >> higher
>> >> to set a trusted location that way.
>> >>
>> >> The front end of the database is in a folder in each user's C drive. I
>> >> use AutoFEUpdater.
>> >>
>> >> The Word document is accessed via a mapped network drive, Y.  The
>> >> location of Y is on this user's PC (paul-pc) which is acting as the
>> >> backend server for the database plus the storage of these shared Word
>> >> docs.
>> >>
>> >> I'm not sure what to try next.
>> >
>> > I've made sure the Windows 7 network type was 'Home'.
>> > The Windows 7 PC is in a Homegroup and Documents are shared.
>> >
>> > I think it might be more to do with the user access control part of
>> > Windows 7 rather than the network side of things.
>> >
>> > Any ideas?
>>
>> Build a test environment by move everything into a local folder that is a
>> trusted location. If the problem continues it is not a security issue.
>> Otherwise move the Word file into the product folder and test again. Keep
>> move parts of the app into product folders until the problem returns.
>
> Hi Ron, how do I make a local folder a trusted location in Office 2003?
> All the files on the computer are part of the intranet in Internet 
> Options, as per the 'file://paul-pc' site listing.
> I have tried moving the mdb and the doc file to a new folder in the user's 
> C:\Documents folder but with the same outcome.

In Access 2010 you can use "Trust Center" in the options dialog.

[toc] | [prev] | [next] | [standalone]

#10604

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-10 02:36 -0700
Message-ID<f1a9ef33-2460-4e02-8c7c-5188f07234ef@googlegroups.com>
In reply to#10600
On Thursday, 9 April 2015 22:02:44 UTC+1, Ron Paii  wrote:

> > On Wednesday, 8 April 2015 21:59:31 UTC+1, Ron Paii  wrote:
> >
> >> > On Tuesday, 7 April 2015 15:26:06 UTC+1, fs  wrote:
> >> >> On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
> >> >> > "fs" wrote in message
> >> >>
> >> >> > > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
> >> >> > >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
> >> >> > >>
> >> >> > >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> >> >> > >> > >> On 31/03/2015 15:56:52, fs wrote:
> >> >> > >> > >> > Hi all,
> >> >> > >> > >> >
> >> >> > >> > >> > I have an Access 2003 database doing a mail merge to Word
> >> >> > >> > >> > 2003. It
> >> >> > >> > >> > works f
> >> >> > >> > >> > ine on two Windows XP machines but not with Windows 7.
> >> >> > >> > >> >
> >> >> > >> > >> > On the Windows 7 machines, a Word application opens and 
> >> >> > >> > >> > the
> >> >> > >> > >> > mail
> >> >> > >> > >> > merge
> >> >> > >> > >> > data is passed (via a txt file) into the .doc file. But 
> >> >> > >> > >> > the
> >> >> > >> > >> > Word
> >> >> > >> > >> > Window
> >> >> > >> > >> > doesn' t take the focus and the user has to click on it in
> >> >> > >> > >> > the
> >> >> > >> > >> > taskbar
> >> >> > >> > >> > (which does n't happen with the XP machines).
> >> >> > >> > >> >
> >> >> > >> > >> > As well as that, the menus are frozen/inaccessible and the
> >> >> > >> > >> > only
> >> >> > >> > >> > button
> >> >> > >> > >> > that works is the big red x in the top right. When the 
> >> >> > >> > >> > user
> >> >> > >> > >> > clicks
> >> >> > >> > >> > that
> >> >> > >> > >> > they a re given the Save As option. They can save the file
> >> >> > >> > >> > and
> >> >> > >> > >> > re-open
> >> >> > >> > >> > it
> >> >> > >> > >> > and edi t as normal.
> >> >> > >> > >> >
> >> >> > >> > >> > My question is what is happening when the initial merge is
> >> >> > >> > >> > happening
> >> >> > >> > >> > and
> >> >> > >> > >> > th e menus are frozen on the Windows 7 machines? Is this a
> >> >> > >> > >> > permissions
> >> >> > >> > >> > issue to do with Windows 7 and programs activating each 
> >> >> > >> > >> > other
> >> >> > >> > >> > using
> >> >> > >> > >> > VBA?
> >> >> > >> > >> >
> >> >> > >> > >> > I'd really appreciate any suggestions. It's been dragging 
> >> >> > >> > >> > on
> >> >> > >> > >> > for
> >> >> > >> > >> > ages
> >> >> > >> > >> > and
> >> >> > >> > >> > I can't find any information about it anywhere.
> >> >> > >> > >> >
> >> >> > >> > >> > Thanks!
> >> >> > >> > >> >
> >> >> > >> > >>
> >> >> > >> > >> Assuming you are usimg VBA do you have things like
> >> >> > >> > >>
> >> >> > >> > >>     Dim WordApp             As Object       ' 
> >> >> > >> > >> Word.Applicaton
> >> >> > >> > >>
> >> >> > >> > >>     Set WordApp = GetObject(, "Word.Application")
> >> >> > >> > >>
> >> >> > >> > >>     WordApp.Visible = True
> >> >> > >> > >>     WordApp.Activate
> >> >> > >> > >>     WordApp.WindowState = 0          'wdWindowStateRestore
> >> >> > >> > >>
> >> >> > >> > >> Phil
> >> >> > >> > >>
> >> >> > >> > >> ---
> >> >> > >> > >> This email has been checked for viruses by Avast antivirus
> >> >> > >> > >> software.
> >> >> > >> > >> http://www.avast.com
> >> >> > >> > >
> >> >> > >> > > Hi Phil,
> >> >> > >> > > Thanks for replying.
> >> >> > >> > >
> >> >> > >> > > I've tried a couple of ways.
> >> >> > >> > >
> >> >> > >> > > The first one was
> >> >> > >> > > ---------------------------------------------------------------------------
> >> >> > >> > > Dim ow As Word.Application
> >> >> > >> > > Dim xDoc As Word.Document
> >> >> > >> > > dim xFilename as string
> >> >> > >> > > dim xDatasource as string
> >> >> > >> > >
> >> >> > >> > > xFilename = "C:\myDoc.doc"
> >> >> > >> > > xDatasource = "C:\myData.csv"
> >> >> > >> > > Set ow = CreateObject("Word.Application")
> >> >> > >> > > Set xDoc = ow.Documents.Open(xFilename)
> >> >> > >> > >
> >> >> > >> > > ow.Documents(x_filename).ActiveWindow.Activate
> >> >> > >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> >> > >> > >
> >> >> > >> > > With Xdoc
> >> >> > >> > >    .MailMerge.OpenDataSource (xDatasource)
> >> >> > >> > >    .MailMerge.Destination = wdSendToNewDocument
> >> >> > >> > >    .MailMerge.Execute
> >> >> > >> > >    .ActiveWindow.Activate
> >> >> > >> > >    .Windows.Application.WindowState = wdWindowStateMaximize
> >> >> > >> > >    .Close
> >> >> > >> > > End With
> >> >> > >> > >
> >> >> > >> > > ow.Visible = True
> >> >> > >> > >
> >> >> > >> > > -----------------------------------------------------------------------------
> >> >> > >> > >
> >> >> > >> > > The second method was more involved but, I thought, 
> >> >> > >> > > bomb-proof
> >> >> > >> > > way of
> >> >> > >> > > bringing any application into focus.  It involves using 
> >> >> > >> > > Windows
> >> >> > >> > > API
> >> >> > >> > > calls
> >> >> > >> > > to read the application's window caption and bring it 
> >> >> > >> > > forward.
> >> >> > >> > >
> >> >> > >> > > Here's the link for it -
> >> >> > >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> >> >> > >> > >
> >> >> > >> > > -----------------------------------------------------------------------------
> >> >> > >> > >
> >> >> > >> > > Both of these methods work on the XP machines but neither 
> >> >> > >> > > works
> >> >> > >> > > on
> >> >> > >> > > the
> >> >> > >> > > Windows 7 machines.
> >> >> > >> > >
> >> >> > >> > > Any ideas?
> >> >> > >> > >
> >> >> > >> > > Thanks, Franc.
> >> >> > >> > >
> >> >> > >> >
> >> >> > >> > Are you storing the file in the base of the "C" drive? Windows 
> >> >> > >> > can
> >> >> > >> > be
> >> >> > >> > touchy
> >> >> > >> > about file in that location, try putting it in a folder.
> >> >> > >>
> >> >> > >> Hi Ron,
> >> >> > >> Sorry, no I'm not storing either file in the C drive.  I just put
> >> >> > >> that to
> >> >> > >> show they were locally stored.  The actual path was a bit long, I
> >> >> > >> thought
> >> >> > >> it would be easier to just put something like that.  My apologies
> >> >> > >> for
> >> >> > >> creating the confusion.
> >> >> > >> Thanks, Franc.
> >> >> > >
> >> >> > > Hi Phil,
> >> >> > > I tried that but it didn't change anything I'm afraid.
> >> >> > > I took your idea though and added a couple of new lines
> >> >> > >
> >> >> > > ow.Activate
> >> >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> >> > >
> >> >> > > So the complete code now looks like this
> >> >> > >
> >> >> > > --------------------------------------------------------
> >> >> > > Dim ow As Word.Application
> >> >> > > Dim xDoc As Word.Document
> >> >> > > dim xFilename as string
> >> >> > > dim xDatasource as string
> >> >> > >
> >> >> > > xFilename = "C:\myDoc.doc"
> >> >> > > xDatasource = "C:\myData.csv"
> >> >> > > Set ow = CreateObject("Word.Application")
> >> >> > > Set xDoc = ow.Documents.Open(xFilename)
> >> >> > >
> >> >> > > ow.Documents(x_filename).ActiveWindow.Activate
> >> >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> >> > >
> >> >> > > With Xdoc
> >> >> > >   .MailMerge.OpenDataSource (xDatasource)
> >> >> > >   .MailMerge.Destination = wdSendToNewDocument
> >> >> > >   .MailMerge.Execute
> >> >> > >   .ActiveWindow.Activate
> >> >> > >   .Windows.Application.WindowState = wdWindowStateMaximize
> >> >> > >   .Close
> >> >> > > End With
> >> >> > >
> >> >> > >    ow.Visible = True
> >> >> > >    ow.Activate
> >> >> > >    ow.Application.WindowState = wdWindowStateMaximize
> >> >> > > set ow = Nothing '(this was there already, just forgot to put into
> >> >> > > the
> >> >> > > post)
> >> >> > > ---------------------------------------------------------------
> >> >> > >
> >> >> > > With these new lines the problem Windows 7 machine reacts a bit
> >> >> > > differently.  Now Word opens in the taskbar and flashes and when 
> >> >> > > the
> >> >> > > user
> >> >> > > clicks on it the menus are not frozen and they can go ahead with
> >> >> > > editing.
> >> >> > > It's progress, but not quite the full solution!
> >> >> > >
> >> >> > > The user has reported that he had the same response of only 
> >> >> > > getting
> >> >> > > the
> >> >> > > flashing button in the taskbar when he was using the database on a
> >> >> > > Windows
> >> >> > > XP machine but which was XP home edition.  The two XP machines 
> >> >> > > which
> >> >> > > work
> >> >> > > as desired are XP Pro machines.  Does this help?
> >> >> > >
> >> >> > > Could the user have changed a Windows setting which stops it
> >> >> > > happening?
> >> >> > >
> >> >> > >
> >> >> > >
> >> >> > Looking a security features Microsoft added since XP; you may need 
> >> >> > to
> >> >> > add
> >> >> > the folder to trusted locations.
> >> >>
> >> >> Hi Ron,
> >> >>
> >> >> I've checked the local intranet settings and this was already in the
> >> >> there:
> >> >>
> >> >> file://paul-pc
> >> >>
> >> >> paul-pc is the name of the computer in question which I think adds all
> >> >> local locations to the intranet(?). He doesn't have Office 2007 or 
> >> >> higher
> >> >> to set a trusted location that way.
> >> >>
> >> >> The front end of the database is in a folder in each user's C drive. I
> >> >> use AutoFEUpdater.
> >> >>
> >> >> The Word document is accessed via a mapped network drive, Y.  The
> >> >> location of Y is on this user's PC (paul-pc) which is acting as the
> >> >> backend server for the database plus the storage of these shared Word
> >> >> docs.
> >> >>
> >> >> I'm not sure what to try next.
> >> >
> >> > I've made sure the Windows 7 network type was 'Home'.
> >> > The Windows 7 PC is in a Homegroup and Documents are shared.
> >> >
> >> > I think it might be more to do with the user access control part of
> >> > Windows 7 rather than the network side of things.
> >> >
> >> > Any ideas?
> >>
> >> Build a test environment by move everything into a local folder that is a
> >> trusted location. If the problem continues it is not a security issue.
> >> Otherwise move the Word file into the product folder and test again. Keep
> >> move parts of the app into product folders until the problem returns.
> >
> > Hi Ron, how do I make a local folder a trusted location in Office 2003?
> > All the files on the computer are part of the intranet in Internet 
> > Options, as per the 'file://paul-pc' site listing.
> > I have tried moving the mdb and the doc file to a new folder in the user's 
> > C:\Documents folder but with the same outcome.
> 
> In Access 2010 you can use "Trust Center" in the options dialog.

Hi Ron, the user has Office 2003.

[toc] | [prev] | [next] | [standalone]

#10605

From"Ron Paii" <None@none.com>
Date2015-04-10 07:08 -0500
Message-ID<mg8eeg$qs6$1@dont-email.me>
In reply to#10604

"fs" <franc.sutherland@googlemail.com> wrote in message 
news:f1a9ef33-2460-4e02-8c7c-5188f07234ef@googlegroups.com...
> On Thursday, 9 April 2015 22:02:44 UTC+1, Ron Paii  wrote:
>
>> > On Wednesday, 8 April 2015 21:59:31 UTC+1, Ron Paii  wrote:
>> >
>> >> > On Tuesday, 7 April 2015 15:26:06 UTC+1, fs  wrote:
>> >> >> On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
>> >> >> > "fs" wrote in message
>> >> >>
>> >> >> > > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
>> >> >> > >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
>> >> >> > >>
>> >> >> > >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
>> >> >> > >> > >> On 31/03/2015 15:56:52, fs wrote:
>> >> >> > >> > >> > Hi all,
>> >> >> > >> > >> >
>> >> >> > >> > >> > I have an Access 2003 database doing a mail merge to 
>> >> >> > >> > >> > Word
>> >> >> > >> > >> > 2003. It
>> >> >> > >> > >> > works f
>> >> >> > >> > >> > ine on two Windows XP machines but not with Windows 7.
>> >> >> > >> > >> >
>> >> >> > >> > >> > On the Windows 7 machines, a Word application opens and
>> >> >> > >> > >> > the
>> >> >> > >> > >> > mail
>> >> >> > >> > >> > merge
>> >> >> > >> > >> > data is passed (via a txt file) into the .doc file. But
>> >> >> > >> > >> > the
>> >> >> > >> > >> > Word
>> >> >> > >> > >> > Window
>> >> >> > >> > >> > doesn' t take the focus and the user has to click on it 
>> >> >> > >> > >> > in
>> >> >> > >> > >> > the
>> >> >> > >> > >> > taskbar
>> >> >> > >> > >> > (which does n't happen with the XP machines).
>> >> >> > >> > >> >
>> >> >> > >> > >> > As well as that, the menus are frozen/inaccessible and 
>> >> >> > >> > >> > the
>> >> >> > >> > >> > only
>> >> >> > >> > >> > button
>> >> >> > >> > >> > that works is the big red x in the top right. When the
>> >> >> > >> > >> > user
>> >> >> > >> > >> > clicks
>> >> >> > >> > >> > that
>> >> >> > >> > >> > they a re given the Save As option. They can save the 
>> >> >> > >> > >> > file
>> >> >> > >> > >> > and
>> >> >> > >> > >> > re-open
>> >> >> > >> > >> > it
>> >> >> > >> > >> > and edi t as normal.
>> >> >> > >> > >> >
>> >> >> > >> > >> > My question is what is happening when the initial merge 
>> >> >> > >> > >> > is
>> >> >> > >> > >> > happening
>> >> >> > >> > >> > and
>> >> >> > >> > >> > th e menus are frozen on the Windows 7 machines? Is 
>> >> >> > >> > >> > this a
>> >> >> > >> > >> > permissions
>> >> >> > >> > >> > issue to do with Windows 7 and programs activating each
>> >> >> > >> > >> > other
>> >> >> > >> > >> > using
>> >> >> > >> > >> > VBA?
>> >> >> > >> > >> >
>> >> >> > >> > >> > I'd really appreciate any suggestions. It's been 
>> >> >> > >> > >> > dragging
>> >> >> > >> > >> > on
>> >> >> > >> > >> > for
>> >> >> > >> > >> > ages
>> >> >> > >> > >> > and
>> >> >> > >> > >> > I can't find any information about it anywhere.
>> >> >> > >> > >> >
>> >> >> > >> > >> > Thanks!
>> >> >> > >> > >> >
>> >> >> > >> > >>
>> >> >> > >> > >> Assuming you are usimg VBA do you have things like
>> >> >> > >> > >>
>> >> >> > >> > >>     Dim WordApp             As Object       '
>> >> >> > >> > >> Word.Applicaton
>> >> >> > >> > >>
>> >> >> > >> > >>     Set WordApp = GetObject(, "Word.Application")
>> >> >> > >> > >>
>> >> >> > >> > >>     WordApp.Visible = True
>> >> >> > >> > >>     WordApp.Activate
>> >> >> > >> > >>     WordApp.WindowState = 0 
>> >> >> > >> > >> 'wdWindowStateRestore
>> >> >> > >> > >>
>> >> >> > >> > >> Phil
>> >> >> > >> > >>
>> >> >> > >> > >> ---
>> >> >> > >> > >> This email has been checked for viruses by Avast 
>> >> >> > >> > >> antivirus
>> >> >> > >> > >> software.
>> >> >> > >> > >> http://www.avast.com
>> >> >> > >> > >
>> >> >> > >> > > Hi Phil,
>> >> >> > >> > > Thanks for replying.
>> >> >> > >> > >
>> >> >> > >> > > I've tried a couple of ways.
>> >> >> > >> > >
>> >> >> > >> > > The first one was
>> >> >> > >> > > ---------------------------------------------------------------------------
>> >> >> > >> > > Dim ow As Word.Application
>> >> >> > >> > > Dim xDoc As Word.Document
>> >> >> > >> > > dim xFilename as string
>> >> >> > >> > > dim xDatasource as string
>> >> >> > >> > >
>> >> >> > >> > > xFilename = "C:\myDoc.doc"
>> >> >> > >> > > xDatasource = "C:\myData.csv"
>> >> >> > >> > > Set ow = CreateObject("Word.Application")
>> >> >> > >> > > Set xDoc = ow.Documents.Open(xFilename)
>> >> >> > >> > >
>> >> >> > >> > > ow.Documents(x_filename).ActiveWindow.Activate
>> >> >> > >> > > ow.Application.WindowState = wdWindowStateMaximize
>> >> >> > >> > >
>> >> >> > >> > > With Xdoc
>> >> >> > >> > >    .MailMerge.OpenDataSource (xDatasource)
>> >> >> > >> > >    .MailMerge.Destination = wdSendToNewDocument
>> >> >> > >> > >    .MailMerge.Execute
>> >> >> > >> > >    .ActiveWindow.Activate
>> >> >> > >> > >    .Windows.Application.WindowState = 
>> >> >> > >> > > wdWindowStateMaximize
>> >> >> > >> > >    .Close
>> >> >> > >> > > End With
>> >> >> > >> > >
>> >> >> > >> > > ow.Visible = True
>> >> >> > >> > >
>> >> >> > >> > > -----------------------------------------------------------------------------
>> >> >> > >> > >
>> >> >> > >> > > The second method was more involved but, I thought,
>> >> >> > >> > > bomb-proof
>> >> >> > >> > > way of
>> >> >> > >> > > bringing any application into focus.  It involves using
>> >> >> > >> > > Windows
>> >> >> > >> > > API
>> >> >> > >> > > calls
>> >> >> > >> > > to read the application's window caption and bring it
>> >> >> > >> > > forward.
>> >> >> > >> > >
>> >> >> > >> > > Here's the link for it -
>> >> >> > >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
>> >> >> > >> > >
>> >> >> > >> > > -----------------------------------------------------------------------------
>> >> >> > >> > >
>> >> >> > >> > > Both of these methods work on the XP machines but neither
>> >> >> > >> > > works
>> >> >> > >> > > on
>> >> >> > >> > > the
>> >> >> > >> > > Windows 7 machines.
>> >> >> > >> > >
>> >> >> > >> > > Any ideas?
>> >> >> > >> > >
>> >> >> > >> > > Thanks, Franc.
>> >> >> > >> > >
>> >> >> > >> >
>> >> >> > >> > Are you storing the file in the base of the "C" drive? 
>> >> >> > >> > Windows
>> >> >> > >> > can
>> >> >> > >> > be
>> >> >> > >> > touchy
>> >> >> > >> > about file in that location, try putting it in a folder.
>> >> >> > >>
>> >> >> > >> Hi Ron,
>> >> >> > >> Sorry, no I'm not storing either file in the C drive.  I just 
>> >> >> > >> put
>> >> >> > >> that to
>> >> >> > >> show they were locally stored.  The actual path was a bit 
>> >> >> > >> long, I
>> >> >> > >> thought
>> >> >> > >> it would be easier to just put something like that.  My 
>> >> >> > >> apologies
>> >> >> > >> for
>> >> >> > >> creating the confusion.
>> >> >> > >> Thanks, Franc.
>> >> >> > >
>> >> >> > > Hi Phil,
>> >> >> > > I tried that but it didn't change anything I'm afraid.
>> >> >> > > I took your idea though and added a couple of new lines
>> >> >> > >
>> >> >> > > ow.Activate
>> >> >> > > ow.Application.WindowState = wdWindowStateMaximize
>> >> >> > >
>> >> >> > > So the complete code now looks like this
>> >> >> > >
>> >> >> > > --------------------------------------------------------
>> >> >> > > Dim ow As Word.Application
>> >> >> > > Dim xDoc As Word.Document
>> >> >> > > dim xFilename as string
>> >> >> > > dim xDatasource as string
>> >> >> > >
>> >> >> > > xFilename = "C:\myDoc.doc"
>> >> >> > > xDatasource = "C:\myData.csv"
>> >> >> > > Set ow = CreateObject("Word.Application")
>> >> >> > > Set xDoc = ow.Documents.Open(xFilename)
>> >> >> > >
>> >> >> > > ow.Documents(x_filename).ActiveWindow.Activate
>> >> >> > > ow.Application.WindowState = wdWindowStateMaximize
>> >> >> > >
>> >> >> > > With Xdoc
>> >> >> > >   .MailMerge.OpenDataSource (xDatasource)
>> >> >> > >   .MailMerge.Destination = wdSendToNewDocument
>> >> >> > >   .MailMerge.Execute
>> >> >> > >   .ActiveWindow.Activate
>> >> >> > >   .Windows.Application.WindowState = wdWindowStateMaximize
>> >> >> > >   .Close
>> >> >> > > End With
>> >> >> > >
>> >> >> > >    ow.Visible = True
>> >> >> > >    ow.Activate
>> >> >> > >    ow.Application.WindowState = wdWindowStateMaximize
>> >> >> > > set ow = Nothing '(this was there already, just forgot to put 
>> >> >> > > into
>> >> >> > > the
>> >> >> > > post)
>> >> >> > > ---------------------------------------------------------------
>> >> >> > >
>> >> >> > > With these new lines the problem Windows 7 machine reacts a bit
>> >> >> > > differently.  Now Word opens in the taskbar and flashes and 
>> >> >> > > when
>> >> >> > > the
>> >> >> > > user
>> >> >> > > clicks on it the menus are not frozen and they can go ahead 
>> >> >> > > with
>> >> >> > > editing.
>> >> >> > > It's progress, but not quite the full solution!
>> >> >> > >
>> >> >> > > The user has reported that he had the same response of only
>> >> >> > > getting
>> >> >> > > the
>> >> >> > > flashing button in the taskbar when he was using the database 
>> >> >> > > on a
>> >> >> > > Windows
>> >> >> > > XP machine but which was XP home edition.  The two XP machines
>> >> >> > > which
>> >> >> > > work
>> >> >> > > as desired are XP Pro machines.  Does this help?
>> >> >> > >
>> >> >> > > Could the user have changed a Windows setting which stops it
>> >> >> > > happening?
>> >> >> > >
>> >> >> > >
>> >> >> > >
>> >> >> > Looking a security features Microsoft added since XP; you may 
>> >> >> > need
>> >> >> > to
>> >> >> > add
>> >> >> > the folder to trusted locations.
>> >> >>
>> >> >> Hi Ron,
>> >> >>
>> >> >> I've checked the local intranet settings and this was already in 
>> >> >> the
>> >> >> there:
>> >> >>
>> >> >> file://paul-pc
>> >> >>
>> >> >> paul-pc is the name of the computer in question which I think adds 
>> >> >> all
>> >> >> local locations to the intranet(?). He doesn't have Office 2007 or
>> >> >> higher
>> >> >> to set a trusted location that way.
>> >> >>
>> >> >> The front end of the database is in a folder in each user's C 
>> >> >> drive. I
>> >> >> use AutoFEUpdater.
>> >> >>
>> >> >> The Word document is accessed via a mapped network drive, Y.  The
>> >> >> location of Y is on this user's PC (paul-pc) which is acting as the
>> >> >> backend server for the database plus the storage of these shared 
>> >> >> Word
>> >> >> docs.
>> >> >>
>> >> >> I'm not sure what to try next.
>> >> >
>> >> > I've made sure the Windows 7 network type was 'Home'.
>> >> > The Windows 7 PC is in a Homegroup and Documents are shared.
>> >> >
>> >> > I think it might be more to do with the user access control part of
>> >> > Windows 7 rather than the network side of things.
>> >> >
>> >> > Any ideas?
>> >>
>> >> Build a test environment by move everything into a local folder that 
>> >> is a
>> >> trusted location. If the problem continues it is not a security issue.
>> >> Otherwise move the Word file into the product folder and test again. 
>> >> Keep
>> >> move parts of the app into product folders until the problem returns.
>> >
>> > Hi Ron, how do I make a local folder a trusted location in Office 2003?
>> > All the files on the computer are part of the intranet in Internet
>> > Options, as per the 'file://paul-pc' site listing.
>> > I have tried moving the mdb and the doc file to a new folder in the 
>> > user's
>> > C:\Documents folder but with the same outcome.
>>
>> In Access 2010 you can use "Trust Center" in the options dialog.
>
> Hi Ron, the user has Office 2003.

I assumed you would be testing on your computer with Access installed. If 
you can't find any other way, create a .reg file for the user's workstation 
and merge it into the registry. The following is one I use for Access 2010 
for users with runtime. The trusted location registry path will be similar 
for Office 2003.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted 
Locations\Location0]
"Path"="C:\\WorkDirectory\\"
"AllowSubfolders"=dword:00000001
"Description"=""
"Date"="9/1/2010 1:56 PM"

[toc] | [prev] | [next] | [standalone]

#10622

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-14 08:47 -0700
Message-ID<db45215e-d06c-4cad-b975-c6b72c32b430@googlegroups.com>
In reply to#10605
On Friday, 10 April 2015 13:08:46 UTC+1, Ron Paii  wrote:

> > On Thursday, 9 April 2015 22:02:44 UTC+1, Ron Paii  wrote:
> >
> >> > On Wednesday, 8 April 2015 21:59:31 UTC+1, Ron Paii  wrote:
> >> >
> >> >> > On Tuesday, 7 April 2015 15:26:06 UTC+1, fs  wrote:
> >> >> >> On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
> >> >> >> > "fs" wrote in message
> >> >> >>
> >> >> >> > > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
> >> >> >> > >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
> >> >> >> > >>
> >> >> >> > >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> >> >> >> > >> > >> On 31/03/2015 15:56:52, fs wrote:
> >> >> >> > >> > >> > Hi all,
> >> >> >> > >> > >> >
> >> >> >> > >> > >> > I have an Access 2003 database doing a mail merge to 
> >> >> >> > >> > >> > Word
> >> >> >> > >> > >> > 2003. It
> >> >> >> > >> > >> > works f
> >> >> >> > >> > >> > ine on two Windows XP machines but not with Windows 7.
> >> >> >> > >> > >> >
> >> >> >> > >> > >> > On the Windows 7 machines, a Word application opens and
> >> >> >> > >> > >> > the
> >> >> >> > >> > >> > mail
> >> >> >> > >> > >> > merge
> >> >> >> > >> > >> > data is passed (via a txt file) into the .doc file. But
> >> >> >> > >> > >> > the
> >> >> >> > >> > >> > Word
> >> >> >> > >> > >> > Window
> >> >> >> > >> > >> > doesn' t take the focus and the user has to click on it 
> >> >> >> > >> > >> > in
> >> >> >> > >> > >> > the
> >> >> >> > >> > >> > taskbar
> >> >> >> > >> > >> > (which does n't happen with the XP machines).
> >> >> >> > >> > >> >
> >> >> >> > >> > >> > As well as that, the menus are frozen/inaccessible and 
> >> >> >> > >> > >> > the
> >> >> >> > >> > >> > only
> >> >> >> > >> > >> > button
> >> >> >> > >> > >> > that works is the big red x in the top right. When the
> >> >> >> > >> > >> > user
> >> >> >> > >> > >> > clicks
> >> >> >> > >> > >> > that
> >> >> >> > >> > >> > they a re given the Save As option. They can save the 
> >> >> >> > >> > >> > file
> >> >> >> > >> > >> > and
> >> >> >> > >> > >> > re-open
> >> >> >> > >> > >> > it
> >> >> >> > >> > >> > and edi t as normal.
> >> >> >> > >> > >> >
> >> >> >> > >> > >> > My question is what is happening when the initial merge 
> >> >> >> > >> > >> > is
> >> >> >> > >> > >> > happening
> >> >> >> > >> > >> > and
> >> >> >> > >> > >> > th e menus are frozen on the Windows 7 machines? Is 
> >> >> >> > >> > >> > this a
> >> >> >> > >> > >> > permissions
> >> >> >> > >> > >> > issue to do with Windows 7 and programs activating each
> >> >> >> > >> > >> > other
> >> >> >> > >> > >> > using
> >> >> >> > >> > >> > VBA?
> >> >> >> > >> > >> >
> >> >> >> > >> > >> > I'd really appreciate any suggestions. It's been 
> >> >> >> > >> > >> > dragging
> >> >> >> > >> > >> > on
> >> >> >> > >> > >> > for
> >> >> >> > >> > >> > ages
> >> >> >> > >> > >> > and
> >> >> >> > >> > >> > I can't find any information about it anywhere.
> >> >> >> > >> > >> >
> >> >> >> > >> > >> > Thanks!
> >> >> >> > >> > >> >
> >> >> >> > >> > >>
> >> >> >> > >> > >> Assuming you are usimg VBA do you have things like
> >> >> >> > >> > >>
> >> >> >> > >> > >>     Dim WordApp             As Object       '
> >> >> >> > >> > >> Word.Applicaton
> >> >> >> > >> > >>
> >> >> >> > >> > >>     Set WordApp = GetObject(, "Word.Application")
> >> >> >> > >> > >>
> >> >> >> > >> > >>     WordApp.Visible = True
> >> >> >> > >> > >>     WordApp.Activate
> >> >> >> > >> > >>     WordApp.WindowState = 0 
> >> >> >> > >> > >> 'wdWindowStateRestore
> >> >> >> > >> > >>
> >> >> >> > >> > >> Phil
> >> >> >> > >> > >>
> >> >> >> > >> > >> ---
> >> >> >> > >> > >> This email has been checked for viruses by Avast 
> >> >> >> > >> > >> antivirus
> >> >> >> > >> > >> software.
> >> >> >> > >> > >> http://www.avast.com
> >> >> >> > >> > >
> >> >> >> > >> > > Hi Phil,
> >> >> >> > >> > > Thanks for replying.
> >> >> >> > >> > >
> >> >> >> > >> > > I've tried a couple of ways.
> >> >> >> > >> > >
> >> >> >> > >> > > The first one was
> >> >> >> > >> > > ---------------------------------------------------------------------------
> >> >> >> > >> > > Dim ow As Word.Application
> >> >> >> > >> > > Dim xDoc As Word.Document
> >> >> >> > >> > > dim xFilename as string
> >> >> >> > >> > > dim xDatasource as string
> >> >> >> > >> > >
> >> >> >> > >> > > xFilename = "C:\myDoc.doc"
> >> >> >> > >> > > xDatasource = "C:\myData.csv"
> >> >> >> > >> > > Set ow = CreateObject("Word.Application")
> >> >> >> > >> > > Set xDoc = ow.Documents.Open(xFilename)
> >> >> >> > >> > >
> >> >> >> > >> > > ow.Documents(x_filename).ActiveWindow.Activate
> >> >> >> > >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> >> >> > >> > >
> >> >> >> > >> > > With Xdoc
> >> >> >> > >> > >    .MailMerge.OpenDataSource (xDatasource)
> >> >> >> > >> > >    .MailMerge.Destination = wdSendToNewDocument
> >> >> >> > >> > >    .MailMerge.Execute
> >> >> >> > >> > >    .ActiveWindow.Activate
> >> >> >> > >> > >    .Windows.Application.WindowState = 
> >> >> >> > >> > > wdWindowStateMaximize
> >> >> >> > >> > >    .Close
> >> >> >> > >> > > End With
> >> >> >> > >> > >
> >> >> >> > >> > > ow.Visible = True
> >> >> >> > >> > >
> >> >> >> > >> > > -----------------------------------------------------------------------------
> >> >> >> > >> > >
> >> >> >> > >> > > The second method was more involved but, I thought,
> >> >> >> > >> > > bomb-proof
> >> >> >> > >> > > way of
> >> >> >> > >> > > bringing any application into focus.  It involves using
> >> >> >> > >> > > Windows
> >> >> >> > >> > > API
> >> >> >> > >> > > calls
> >> >> >> > >> > > to read the application's window caption and bring it
> >> >> >> > >> > > forward.
> >> >> >> > >> > >
> >> >> >> > >> > > Here's the link for it -
> >> >> >> > >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> >> >> >> > >> > >
> >> >> >> > >> > > -----------------------------------------------------------------------------
> >> >> >> > >> > >
> >> >> >> > >> > > Both of these methods work on the XP machines but neither
> >> >> >> > >> > > works
> >> >> >> > >> > > on
> >> >> >> > >> > > the
> >> >> >> > >> > > Windows 7 machines.
> >> >> >> > >> > >
> >> >> >> > >> > > Any ideas?
> >> >> >> > >> > >
> >> >> >> > >> > > Thanks, Franc.
> >> >> >> > >> > >
> >> >> >> > >> >
> >> >> >> > >> > Are you storing the file in the base of the "C" drive? 
> >> >> >> > >> > Windows
> >> >> >> > >> > can
> >> >> >> > >> > be
> >> >> >> > >> > touchy
> >> >> >> > >> > about file in that location, try putting it in a folder.
> >> >> >> > >>
> >> >> >> > >> Hi Ron,
> >> >> >> > >> Sorry, no I'm not storing either file in the C drive.  I just 
> >> >> >> > >> put
> >> >> >> > >> that to
> >> >> >> > >> show they were locally stored.  The actual path was a bit 
> >> >> >> > >> long, I
> >> >> >> > >> thought
> >> >> >> > >> it would be easier to just put something like that.  My 
> >> >> >> > >> apologies
> >> >> >> > >> for
> >> >> >> > >> creating the confusion.
> >> >> >> > >> Thanks, Franc.
> >> >> >> > >
> >> >> >> > > Hi Phil,
> >> >> >> > > I tried that but it didn't change anything I'm afraid.
> >> >> >> > > I took your idea though and added a couple of new lines
> >> >> >> > >
> >> >> >> > > ow.Activate
> >> >> >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> >> >> > >
> >> >> >> > > So the complete code now looks like this
> >> >> >> > >
> >> >> >> > > --------------------------------------------------------
> >> >> >> > > Dim ow As Word.Application
> >> >> >> > > Dim xDoc As Word.Document
> >> >> >> > > dim xFilename as string
> >> >> >> > > dim xDatasource as string
> >> >> >> > >
> >> >> >> > > xFilename = "C:\myDoc.doc"
> >> >> >> > > xDatasource = "C:\myData.csv"
> >> >> >> > > Set ow = CreateObject("Word.Application")
> >> >> >> > > Set xDoc = ow.Documents.Open(xFilename)
> >> >> >> > >
> >> >> >> > > ow.Documents(x_filename).ActiveWindow.Activate
> >> >> >> > > ow.Application.WindowState = wdWindowStateMaximize
> >> >> >> > >
> >> >> >> > > With Xdoc
> >> >> >> > >   .MailMerge.OpenDataSource (xDatasource)
> >> >> >> > >   .MailMerge.Destination = wdSendToNewDocument
> >> >> >> > >   .MailMerge.Execute
> >> >> >> > >   .ActiveWindow.Activate
> >> >> >> > >   .Windows.Application.WindowState = wdWindowStateMaximize
> >> >> >> > >   .Close
> >> >> >> > > End With
> >> >> >> > >
> >> >> >> > >    ow.Visible = True
> >> >> >> > >    ow.Activate
> >> >> >> > >    ow.Application.WindowState = wdWindowStateMaximize
> >> >> >> > > set ow = Nothing '(this was there already, just forgot to put 
> >> >> >> > > into
> >> >> >> > > the
> >> >> >> > > post)
> >> >> >> > > ---------------------------------------------------------------
> >> >> >> > >
> >> >> >> > > With these new lines the problem Windows 7 machine reacts a bit
> >> >> >> > > differently.  Now Word opens in the taskbar and flashes and 
> >> >> >> > > when
> >> >> >> > > the
> >> >> >> > > user
> >> >> >> > > clicks on it the menus are not frozen and they can go ahead 
> >> >> >> > > with
> >> >> >> > > editing.
> >> >> >> > > It's progress, but not quite the full solution!
> >> >> >> > >
> >> >> >> > > The user has reported that he had the same response of only
> >> >> >> > > getting
> >> >> >> > > the
> >> >> >> > > flashing button in the taskbar when he was using the database 
> >> >> >> > > on a
> >> >> >> > > Windows
> >> >> >> > > XP machine but which was XP home edition.  The two XP machines
> >> >> >> > > which
> >> >> >> > > work
> >> >> >> > > as desired are XP Pro machines.  Does this help?
> >> >> >> > >
> >> >> >> > > Could the user have changed a Windows setting which stops it
> >> >> >> > > happening?
> >> >> >> > >
> >> >> >> > >
> >> >> >> > >
> >> >> >> > Looking a security features Microsoft added since XP; you may 
> >> >> >> > need
> >> >> >> > to
> >> >> >> > add
> >> >> >> > the folder to trusted locations.
> >> >> >>
> >> >> >> Hi Ron,
> >> >> >>
> >> >> >> I've checked the local intranet settings and this was already in 
> >> >> >> the
> >> >> >> there:
> >> >> >>
> >> >> >> file://paul-pc
> >> >> >>
> >> >> >> paul-pc is the name of the computer in question which I think adds 
> >> >> >> all
> >> >> >> local locations to the intranet(?). He doesn't have Office 2007 or
> >> >> >> higher
> >> >> >> to set a trusted location that way.
> >> >> >>
> >> >> >> The front end of the database is in a folder in each user's C 
> >> >> >> drive. I
> >> >> >> use AutoFEUpdater.
> >> >> >>
> >> >> >> The Word document is accessed via a mapped network drive, Y.  The
> >> >> >> location of Y is on this user's PC (paul-pc) which is acting as the
> >> >> >> backend server for the database plus the storage of these shared 
> >> >> >> Word
> >> >> >> docs.
> >> >> >>
> >> >> >> I'm not sure what to try next.
> >> >> >
> >> >> > I've made sure the Windows 7 network type was 'Home'.
> >> >> > The Windows 7 PC is in a Homegroup and Documents are shared.
> >> >> >
> >> >> > I think it might be more to do with the user access control part of
> >> >> > Windows 7 rather than the network side of things.
> >> >> >
> >> >> > Any ideas?
> >> >>
> >> >> Build a test environment by move everything into a local folder that 
> >> >> is a
> >> >> trusted location. If the problem continues it is not a security issue.
> >> >> Otherwise move the Word file into the product folder and test again. 
> >> >> Keep
> >> >> move parts of the app into product folders until the problem returns.
> >> >
> >> > Hi Ron, how do I make a local folder a trusted location in Office 2003?
> >> > All the files on the computer are part of the intranet in Internet
> >> > Options, as per the 'file://paul-pc' site listing.
> >> > I have tried moving the mdb and the doc file to a new folder in the 
> >> > user's
> >> > C:\Documents folder but with the same outcome.
> >>
> >> In Access 2010 you can use "Trust Center" in the options dialog.
> >
> > Hi Ron, the user has Office 2003.
> 
> I assumed you would be testing on your computer with Access installed. If 
> you can't find any other way, create a .reg file for the user's workstation 
> and merge it into the registry. The following is one I use for Access 2010 
> for users with runtime. The trusted location registry path will be similar 
> for Office 2003.
> 
> Windows Registry Editor Version 5.00
> 
> [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted 
> Locations\Location0]
> "Path"="C:\\WorkDirectory\\"
> "AllowSubfolders"=dword:00000001
> "Description"=""
> "Date"="9/1/2010 1:56 PM"

Hi Ron,
Yes, I have Access 2013 on a Windows 7 and Access 2010 on Windows XP, both of which are working fine.  It's the user who has Access 2003 on Windows 7.
I'll try your reg edit and report back.  
Thanks, Franc.

[toc] | [prev] | [next] | [standalone]

#10674

Fromfs <franc.sutherland@googlemail.com>
Date2015-04-27 07:51 -0700
Message-ID<a7a0f46c-73b7-4c47-809e-4a495973f2a4@googlegroups.com>
In reply to#10622
On Tuesday, 14 April 2015 16:47:19 UTC+1, fs  wrote:
> On Friday, 10 April 2015 13:08:46 UTC+1, Ron Paii  wrote:
> 
> > > On Thursday, 9 April 2015 22:02:44 UTC+1, Ron Paii  wrote:
> > >
> > >> > On Wednesday, 8 April 2015 21:59:31 UTC+1, Ron Paii  wrote:
> > >> >
> > >> >> > On Tuesday, 7 April 2015 15:26:06 UTC+1, fs  wrote:
> > >> >> >> On Thursday, 2 April 2015 13:02:58 UTC+1, Ron Paii  wrote:
> > >> >> >> > "fs" wrote in message
> > >> >> >>
> > >> >> >> > > On Thursday, 2 April 2015 09:20:21 UTC+1, fs  wrote:
> > >> >> >> > >> On Wednesday, 1 April 2015 21:14:50 UTC+1, Ron Paii  wrote:
> > >> >> >> > >>
> > >> >> >> > >> > > On Tuesday, 31 March 2015 16:35:23 UTC+1, Phil  wrote:
> > >> >> >> > >> > >> On 31/03/2015 15:56:52, fs wrote:
> > >> >> >> > >> > >> > Hi all,
> > >> >> >> > >> > >> >
> > >> >> >> > >> > >> > I have an Access 2003 database doing a mail merge to 
> > >> >> >> > >> > >> > Word
> > >> >> >> > >> > >> > 2003. It
> > >> >> >> > >> > >> > works f
> > >> >> >> > >> > >> > ine on two Windows XP machines but not with Windows 7.
> > >> >> >> > >> > >> >
> > >> >> >> > >> > >> > On the Windows 7 machines, a Word application opens and
> > >> >> >> > >> > >> > the
> > >> >> >> > >> > >> > mail
> > >> >> >> > >> > >> > merge
> > >> >> >> > >> > >> > data is passed (via a txt file) into the .doc file. But
> > >> >> >> > >> > >> > the
> > >> >> >> > >> > >> > Word
> > >> >> >> > >> > >> > Window
> > >> >> >> > >> > >> > doesn' t take the focus and the user has to click on it 
> > >> >> >> > >> > >> > in
> > >> >> >> > >> > >> > the
> > >> >> >> > >> > >> > taskbar
> > >> >> >> > >> > >> > (which does n't happen with the XP machines).
> > >> >> >> > >> > >> >
> > >> >> >> > >> > >> > As well as that, the menus are frozen/inaccessible and 
> > >> >> >> > >> > >> > the
> > >> >> >> > >> > >> > only
> > >> >> >> > >> > >> > button
> > >> >> >> > >> > >> > that works is the big red x in the top right. When the
> > >> >> >> > >> > >> > user
> > >> >> >> > >> > >> > clicks
> > >> >> >> > >> > >> > that
> > >> >> >> > >> > >> > they a re given the Save As option. They can save the 
> > >> >> >> > >> > >> > file
> > >> >> >> > >> > >> > and
> > >> >> >> > >> > >> > re-open
> > >> >> >> > >> > >> > it
> > >> >> >> > >> > >> > and edi t as normal.
> > >> >> >> > >> > >> >
> > >> >> >> > >> > >> > My question is what is happening when the initial merge 
> > >> >> >> > >> > >> > is
> > >> >> >> > >> > >> > happening
> > >> >> >> > >> > >> > and
> > >> >> >> > >> > >> > th e menus are frozen on the Windows 7 machines? Is 
> > >> >> >> > >> > >> > this a
> > >> >> >> > >> > >> > permissions
> > >> >> >> > >> > >> > issue to do with Windows 7 and programs activating each
> > >> >> >> > >> > >> > other
> > >> >> >> > >> > >> > using
> > >> >> >> > >> > >> > VBA?
> > >> >> >> > >> > >> >
> > >> >> >> > >> > >> > I'd really appreciate any suggestions. It's been 
> > >> >> >> > >> > >> > dragging
> > >> >> >> > >> > >> > on
> > >> >> >> > >> > >> > for
> > >> >> >> > >> > >> > ages
> > >> >> >> > >> > >> > and
> > >> >> >> > >> > >> > I can't find any information about it anywhere.
> > >> >> >> > >> > >> >
> > >> >> >> > >> > >> > Thanks!
> > >> >> >> > >> > >> >
> > >> >> >> > >> > >>
> > >> >> >> > >> > >> Assuming you are usimg VBA do you have things like
> > >> >> >> > >> > >>
> > >> >> >> > >> > >>     Dim WordApp             As Object       '
> > >> >> >> > >> > >> Word.Applicaton
> > >> >> >> > >> > >>
> > >> >> >> > >> > >>     Set WordApp = GetObject(, "Word.Application")
> > >> >> >> > >> > >>
> > >> >> >> > >> > >>     WordApp.Visible = True
> > >> >> >> > >> > >>     WordApp.Activate
> > >> >> >> > >> > >>     WordApp.WindowState = 0 
> > >> >> >> > >> > >> 'wdWindowStateRestore
> > >> >> >> > >> > >>
> > >> >> >> > >> > >> Phil
> > >> >> >> > >> > >>
> > >> >> >> > >> > >> ---
> > >> >> >> > >> > >> This email has been checked for viruses by Avast 
> > >> >> >> > >> > >> antivirus
> > >> >> >> > >> > >> software.
> > >> >> >> > >> > >> http://www.avast.com
> > >> >> >> > >> > >
> > >> >> >> > >> > > Hi Phil,
> > >> >> >> > >> > > Thanks for replying.
> > >> >> >> > >> > >
> > >> >> >> > >> > > I've tried a couple of ways.
> > >> >> >> > >> > >
> > >> >> >> > >> > > The first one was
> > >> >> >> > >> > > ---------------------------------------------------------------------------
> > >> >> >> > >> > > Dim ow As Word.Application
> > >> >> >> > >> > > Dim xDoc As Word.Document
> > >> >> >> > >> > > dim xFilename as string
> > >> >> >> > >> > > dim xDatasource as string
> > >> >> >> > >> > >
> > >> >> >> > >> > > xFilename = "C:\myDoc.doc"
> > >> >> >> > >> > > xDatasource = "C:\myData.csv"
> > >> >> >> > >> > > Set ow = CreateObject("Word.Application")
> > >> >> >> > >> > > Set xDoc = ow.Documents.Open(xFilename)
> > >> >> >> > >> > >
> > >> >> >> > >> > > ow.Documents(x_filename).ActiveWindow.Activate
> > >> >> >> > >> > > ow.Application.WindowState = wdWindowStateMaximize
> > >> >> >> > >> > >
> > >> >> >> > >> > > With Xdoc
> > >> >> >> > >> > >    .MailMerge.OpenDataSource (xDatasource)
> > >> >> >> > >> > >    .MailMerge.Destination = wdSendToNewDocument
> > >> >> >> > >> > >    .MailMerge.Execute
> > >> >> >> > >> > >    .ActiveWindow.Activate
> > >> >> >> > >> > >    .Windows.Application.WindowState = 
> > >> >> >> > >> > > wdWindowStateMaximize
> > >> >> >> > >> > >    .Close
> > >> >> >> > >> > > End With
> > >> >> >> > >> > >
> > >> >> >> > >> > > ow.Visible = True
> > >> >> >> > >> > >
> > >> >> >> > >> > > -----------------------------------------------------------------------------
> > >> >> >> > >> > >
> > >> >> >> > >> > > The second method was more involved but, I thought,
> > >> >> >> > >> > > bomb-proof
> > >> >> >> > >> > > way of
> > >> >> >> > >> > > bringing any application into focus.  It involves using
> > >> >> >> > >> > > Windows
> > >> >> >> > >> > > API
> > >> >> >> > >> > > calls
> > >> >> >> > >> > > to read the application's window caption and bring it
> > >> >> >> > >> > > forward.
> > >> >> >> > >> > >
> > >> >> >> > >> > > Here's the link for it -
> > >> >> >> > >> > > http://www.everythingaccess.com/tutorials.asp?ID=Bring-an-external-application-window-to-the-foreground
> > >> >> >> > >> > >
> > >> >> >> > >> > > -----------------------------------------------------------------------------
> > >> >> >> > >> > >
> > >> >> >> > >> > > Both of these methods work on the XP machines but neither
> > >> >> >> > >> > > works
> > >> >> >> > >> > > on
> > >> >> >> > >> > > the
> > >> >> >> > >> > > Windows 7 machines.
> > >> >> >> > >> > >
> > >> >> >> > >> > > Any ideas?
> > >> >> >> > >> > >
> > >> >> >> > >> > > Thanks, Franc.
> > >> >> >> > >> > >
> > >> >> >> > >> >
> > >> >> >> > >> > Are you storing the file in the base of the "C" drive? 
> > >> >> >> > >> > Windows
> > >> >> >> > >> > can
> > >> >> >> > >> > be
> > >> >> >> > >> > touchy
> > >> >> >> > >> > about file in that location, try putting it in a folder.
> > >> >> >> > >>
> > >> >> >> > >> Hi Ron,
> > >> >> >> > >> Sorry, no I'm not storing either file in the C drive.  I just 
> > >> >> >> > >> put
> > >> >> >> > >> that to
> > >> >> >> > >> show they were locally stored.  The actual path was a bit 
> > >> >> >> > >> long, I
> > >> >> >> > >> thought
> > >> >> >> > >> it would be easier to just put something like that.  My 
> > >> >> >> > >> apologies
> > >> >> >> > >> for
> > >> >> >> > >> creating the confusion.
> > >> >> >> > >> Thanks, Franc.
> > >> >> >> > >
> > >> >> >> > > Hi Phil,
> > >> >> >> > > I tried that but it didn't change anything I'm afraid.
> > >> >> >> > > I took your idea though and added a couple of new lines
> > >> >> >> > >
> > >> >> >> > > ow.Activate
> > >> >> >> > > ow.Application.WindowState = wdWindowStateMaximize
> > >> >> >> > >
> > >> >> >> > > So the complete code now looks like this
> > >> >> >> > >
> > >> >> >> > > --------------------------------------------------------
> > >> >> >> > > Dim ow As Word.Application
> > >> >> >> > > Dim xDoc As Word.Document
> > >> >> >> > > dim xFilename as string
> > >> >> >> > > dim xDatasource as string
> > >> >> >> > >
> > >> >> >> > > xFilename = "C:\myDoc.doc"
> > >> >> >> > > xDatasource = "C:\myData.csv"
> > >> >> >> > > Set ow = CreateObject("Word.Application")
> > >> >> >> > > Set xDoc = ow.Documents.Open(xFilename)
> > >> >> >> > >
> > >> >> >> > > ow.Documents(x_filename).ActiveWindow.Activate
> > >> >> >> > > ow.Application.WindowState = wdWindowStateMaximize
> > >> >> >> > >
> > >> >> >> > > With Xdoc
> > >> >> >> > >   .MailMerge.OpenDataSource (xDatasource)
> > >> >> >> > >   .MailMerge.Destination = wdSendToNewDocument
> > >> >> >> > >   .MailMerge.Execute
> > >> >> >> > >   .ActiveWindow.Activate
> > >> >> >> > >   .Windows.Application.WindowState = wdWindowStateMaximize
> > >> >> >> > >   .Close
> > >> >> >> > > End With
> > >> >> >> > >
> > >> >> >> > >    ow.Visible = True
> > >> >> >> > >    ow.Activate
> > >> >> >> > >    ow.Application.WindowState = wdWindowStateMaximize
> > >> >> >> > > set ow = Nothing '(this was there already, just forgot to put 
> > >> >> >> > > into
> > >> >> >> > > the
> > >> >> >> > > post)
> > >> >> >> > > ---------------------------------------------------------------
> > >> >> >> > >
> > >> >> >> > > With these new lines the problem Windows 7 machine reacts a bit
> > >> >> >> > > differently.  Now Word opens in the taskbar and flashes and 
> > >> >> >> > > when
> > >> >> >> > > the
> > >> >> >> > > user
> > >> >> >> > > clicks on it the menus are not frozen and they can go ahead 
> > >> >> >> > > with
> > >> >> >> > > editing.
> > >> >> >> > > It's progress, but not quite the full solution!
> > >> >> >> > >
> > >> >> >> > > The user has reported that he had the same response of only
> > >> >> >> > > getting
> > >> >> >> > > the
> > >> >> >> > > flashing button in the taskbar when he was using the database 
> > >> >> >> > > on a
> > >> >> >> > > Windows
> > >> >> >> > > XP machine but which was XP home edition.  The two XP machines
> > >> >> >> > > which
> > >> >> >> > > work
> > >> >> >> > > as desired are XP Pro machines.  Does this help?
> > >> >> >> > >
> > >> >> >> > > Could the user have changed a Windows setting which stops it
> > >> >> >> > > happening?
> > >> >> >> > >
> > >> >> >> > >
> > >> >> >> > >
> > >> >> >> > Looking a security features Microsoft added since XP; you may 
> > >> >> >> > need
> > >> >> >> > to
> > >> >> >> > add
> > >> >> >> > the folder to trusted locations.
> > >> >> >>
> > >> >> >> Hi Ron,
> > >> >> >>
> > >> >> >> I've checked the local intranet settings and this was already in 
> > >> >> >> the
> > >> >> >> there:
> > >> >> >>
> > >> >> >> file://paul-pc
> > >> >> >>
> > >> >> >> paul-pc is the name of the computer in question which I think adds 
> > >> >> >> all
> > >> >> >> local locations to the intranet(?). He doesn't have Office 2007 or
> > >> >> >> higher
> > >> >> >> to set a trusted location that way.
> > >> >> >>
> > >> >> >> The front end of the database is in a folder in each user's C 
> > >> >> >> drive. I
> > >> >> >> use AutoFEUpdater.
> > >> >> >>
> > >> >> >> The Word document is accessed via a mapped network drive, Y.  The
> > >> >> >> location of Y is on this user's PC (paul-pc) which is acting as the
> > >> >> >> backend server for the database plus the storage of these shared 
> > >> >> >> Word
> > >> >> >> docs.
> > >> >> >>
> > >> >> >> I'm not sure what to try next.
> > >> >> >
> > >> >> > I've made sure the Windows 7 network type was 'Home'.
> > >> >> > The Windows 7 PC is in a Homegroup and Documents are shared.
> > >> >> >
> > >> >> > I think it might be more to do with the user access control part of
> > >> >> > Windows 7 rather than the network side of things.
> > >> >> >
> > >> >> > Any ideas?
> > >> >>
> > >> >> Build a test environment by move everything into a local folder that 
> > >> >> is a
> > >> >> trusted location. If the problem continues it is not a security issue.
> > >> >> Otherwise move the Word file into the product folder and test again. 
> > >> >> Keep
> > >> >> move parts of the app into product folders until the problem returns.
> > >> >
> > >> > Hi Ron, how do I make a local folder a trusted location in Office 2003?
> > >> > All the files on the computer are part of the intranet in Internet
> > >> > Options, as per the 'file://paul-pc' site listing.
> > >> > I have tried moving the mdb and the doc file to a new folder in the 
> > >> > user's
> > >> > C:\Documents folder but with the same outcome.
> > >>
> > >> In Access 2010 you can use "Trust Center" in the options dialog.
> > >
> > > Hi Ron, the user has Office 2003.
> > 
> > I assumed you would be testing on your computer with Access installed. If 
> > you can't find any other way, create a .reg file for the user's workstation 
> > and merge it into the registry. The following is one I use for Access 2010 
> > for users with runtime. The trusted location registry path will be similar 
> > for Office 2003.
> > 
> > Windows Registry Editor Version 5.00
> > 
> > [HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Access\Security\Trusted 
> > Locations\Location0]
> > "Path"="C:\\WorkDirectory\\"
> > "AllowSubfolders"=dword:00000001
> > "Description"=""
> > "Date"="9/1/2010 1:56 PM"
> 
> Hi Ron,
> Yes, I have Access 2013 on a Windows 7 and Access 2010 on Windows XP, both of which are working fine.  It's the user who has Access 2003 on Windows 7.
> I'll try your reg edit and report back.  
> Thanks, Franc.

Hi, sorry for the delay in responding, was called away.
I'm afraid the reg edit didn't help.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.ms-access

csiph-web