No data in Word merge when filter Access

[Søren Dalhoff]

I have a Access connected to Sharepoint list and Word merge setup connected
to the Access. The Word merge showing the Access data (Sharepoint list data).
So far so good. Then if setting a filter on on the Access the filter is
working fine in Access. But the Word merge data is then 0 (No data at all)

[Daiya Mitchell]

Hi Soren,

You are back in the MacWord group again. Try here:
http://www.microsoft.com/office/community/en-us/default.mspx

[Peter Jamieson]

Most likely problem given the info. so far: If your filter uses old-style
wildcard * or ? then
a. it won't work if you connect to Access using the default connection
method in Word 2002/2003 (OLE DB).
b. if you change the wildcards to the ANSI-92 SQL equivalents % and _ then
the query should work from Word + OLE DB but it will probably only work
within Access if you also modify your database to use the ANSI syntax - see
Access Tools|Options|Tables/Queries, and bear in mind that making this
change may impact many other things.

And you're in the wrong list as Daiya says...

Peter Jamieson

"Søren Dalhoff" <SrenD...@discussions.microsoft.com> wrote in message
news:15E9B2EC-D89B-44E1...@microsoft.com...

[Søren Dalhoff]

When creating a new post and selecting "Word" I cant see it's under Mac. -
Sorry

[Søren Dalhoff]

Does the same goes for office 2007 (that is what i'm using)?

BTW Peter. Awesome job you are doing here in the community. Your name is all
over :-)

[Peter Jamieson]

> Does the same goes for office 2007 (that is what i'm using)?

I don't know for sure, because
a. the option to change database from the "Jet SQL" format to the "ANSI
SQL" format seems to have disappeared in Access 2007. Help doesn't help
b. the Access 2007 documentation is a bit ambiguous on this subject. At one
point is says that "the ANSI SQL wildcards are only available when using the
Microsoft Access database engine and the Microsoft Access 2007 OLE DB
Provider. if you try to use the ANSI SQL wildcards through Office Access
2007 or DAO, then they wil be interpreted as literals"
c. sure enough databases created in Access 2007 seem only to recognise *
and ?, but Access 2007 seems to recognise % and _ just fine in databases
that already had ANSI support set, and does not recognise * and ?

However, the ACE OLE DB Provider is no different from the Jet OLE DB
provider in that it only recognises % and _, but I haven't verified that.

BTW, I'm interested that you can see your SharePoint linked tables at all
from Word - I can't, here, unless I open them from VBA (and I haven't tried
that on 2007).

> Your name is all over :-)

Always a worry...:-)

Peter Jamieson
"Søren Dalhoff" <SrenD...@discussions.microsoft.com> wrote in message

news:44C54799-A0A8-448E...@microsoft.com...

[Daiya Mitchell]

Hi Soren,

Not your fault--but can you share the link you are posting from? Or do
you remember what process brings you here? Maybe we can get something
improved. There are many different ways to access the groups and paths
to take to them, and we can't figure out where the miscommunication is,
so no one can fix it.

[Peter Jamieson]

For anyone interested, a further look suggests that
a. The ACE OLE DB provider does only recognise the ANSI wildcards
b. it is possible to change an Access 2007 accdb to use ANSI syntax using
the VBA comand

Application SetOption "ANSI Query Mode", True

I have no idea whether there is an equivalent option lurking in the UI
somewhere.

Peter Jamieson
"Peter Jamieson" <p...@KillmapSpjjnet.demon.co.uk> wrote in message
news:OY04$eXSHH...@TK2MSFTNGP03.phx.gbl...