View Single Post
  #3   Report Post  
Posted to microsoft.public.word.docmanagement
Peter Jamieson Peter Jamieson is offline
external usenet poster
 
Posts: 4,582
Default Issue with inserting an Access database to Word

I'm not sure I can help as I cannot replicate this problem right now. But...

Which version of Word/Access? (can you provide the complete version
number including SP etc. from the Help-About or Office button-Word
Options-Resources-About - e.g. here I have
Word 2007 (12.0.6514.5000) SP2 MSO (12.0.6425.1000)
but even
"Word 2007 SP2"
might be handy.

Is the database a .accdb, .mdb, or what? Is it standalone or a front end
to something else, and if so, what?

When you connect to the data, are you seeing a "Confirm Data SOurce"
dialog box that lets you select a particular type of connection (OLE
DB/ODBC/DDE?) If so, which are you choosing?

What type of server/share is the database on - e.g. is it on a shared
folder on a Windows domain server?

Are you in a position to create a database in the same server folder
with the same permissions and shareability, but which in fact no-one
else is sharing? If so, are you able to insert data using that?

FWIW if you are using Word 2007, a number of people mentioned that they
had difficulty connecting to .mdb s over a network, or were seeing
corrupted data etc. However, it's possible that some of those problems
have been fixed in Word 2007 SP2 or even earlier.


Peter Jamieson

http://tips.pjmsn.me.uk

On 14/04/2010 01:21, Kristina wrote:
I'm attempting to insert a shared Access database into Word using the Word
"Insert Database" tool.

I select the database query to run from, limit the fields, and insert the
data - then I get an hourglass for a bit and when that's done I get
nothing... not even an error message. There is data in the fields I'm pulling
(I double-checked).

The Word document at that point acts like I've changed it (requests a save
on close), but there is no data on the screen.

This process works when I create a local copy of the database that no other
user is in, but not when I use the shared database on our server. Is this a
known issue with permissions? Or is there a work-around that I'm missing?