hexOffender
asked on
Error Accessing Word Document
My application pulls some patient data from a table and prints it on a Word Document.
It is working fine for one user, but the other user gets the "error Accessing Word Document". The word docs are on a network share. When I setup the second user, she initially got the same error, but it went away when I gave her permissions on the folder where the docs are stored. Both users have the same permissions, and the drive and folder are accessible to both.The docs used by the App are in a folder that only these two users have access to( and me of course), so I know that it is not a file lock issue. Where else should I look to see why the one user cannot access the word docs?
It is working fine for one user, but the other user gets the "error Accessing Word Document". The word docs are on a network share. When I setup the second user, she initially got the same error, but it went away when I gave her permissions on the folder where the docs are stored. Both users have the same permissions, and the drive and folder are accessible to both.The docs used by the App are in a folder that only these two users have access to( and me of course), so I know that it is not a file lock issue. Where else should I look to see why the one user cannot access the word docs?
Do they have the same version of Word installed on their PC. If you are using early binding you have to make sure that the Word verrsion is the same as referenced library
ASKER
I bet thats it, she has Word 2002 and I and the working user have Word 2003.
Can you esplain more about the early vs. late binding? Well more to the point, what is the way to make this work for all the versions ( at least the most recent ones)
Can you esplain more about the early vs. late binding? Well more to the point, what is the way to make this work for all the versions ( at least the most recent ones)
During an early binding you create a reference to the Word object. During late binding you create an object at a run time. Late binding will use the version of the Word existing on the user PC
Example
'early - ref to Excel Lib
' Dim testexcel As New Excel.Application()
'Late - no ref
Dim testexcel As Object
testexcel = CreateObject("Excel.Applic
... code...
a few pro's and con's for early and late binding.
early binding
pro's
- Ease of developing, in the VB-IDE, when using early binding, you have have context sensitive help,
dropdowns and other stuff which makes developing very productive.
- Faster, early bound code executes faster, because it doesn't have to search the registry for registration
information, cause it is compiled into the exe
con's
- If the target computer does not have the file, an error will ocuur which can't be trapped, forcing
the application to quit without terminating properly, so no unload events are triggered, which can lead
to memory leaks and stuff
- Version dependant. When using early bound refferences, if a file is found, but the version is lower,
the program will give an error and quit in the way described above.
late binding
pro's
- Trappable errors: If a file cannot be found, a runtime error occurs which can be trapped, enabeling you
to execute other code to terminate the application the way it should.
- Version independant. If you don't specify a version, the system will use the highest version it finds. So if
a computer needs ADO, like say 2.5, and the target computer only has ADO 2.1 installed, there's a chance
the program still works as it should, if not version dependant functions are used.
- Flexibility: when using late bound, you can create objects when you only have the name. You can even
use strings which hold the name of the object, and create it from that.
- Polymorphism: this is a more advanced topic, but I'll just stick to the fact that this can only be done using
late bound objects
Example
'early - ref to Excel Lib
' Dim testexcel As New Excel.Application()
'Late - no ref
Dim testexcel As Object
testexcel = CreateObject("Excel.Applic
... code...
a few pro's and con's for early and late binding.
early binding
pro's
- Ease of developing, in the VB-IDE, when using early binding, you have have context sensitive help,
dropdowns and other stuff which makes developing very productive.
- Faster, early bound code executes faster, because it doesn't have to search the registry for registration
information, cause it is compiled into the exe
con's
- If the target computer does not have the file, an error will ocuur which can't be trapped, forcing
the application to quit without terminating properly, so no unload events are triggered, which can lead
to memory leaks and stuff
- Version dependant. When using early bound refferences, if a file is found, but the version is lower,
the program will give an error and quit in the way described above.
late binding
pro's
- Trappable errors: If a file cannot be found, a runtime error occurs which can be trapped, enabeling you
to execute other code to terminate the application the way it should.
- Version independant. If you don't specify a version, the system will use the highest version it finds. So if
a computer needs ADO, like say 2.5, and the target computer only has ADO 2.1 installed, there's a chance
the program still works as it should, if not version dependant functions are used.
- Flexibility: when using late bound, you can create objects when you only have the name. You can even
use strings which hold the name of the object, and create it from that.
- Polymorphism: this is a more advanced topic, but I'll just stick to the fact that this can only be done using
late bound objects
ASKER
Ok,
here is the code i am using,
Dim wordApp As Word.Application
wordApp = CreateObject("Word.Applica
Dim wordDoc = New Word.Document
So which type of binding would you say it is?
here is the code i am using,
Dim wordApp As Word.Application
wordApp = CreateObject("Word.Applica
Dim wordDoc = New Word.Document
So which type of binding would you say it is?
ASKER
Ok I see now , I am late binding as I create the object at runtime, but that does not explain why the error with access to the Documents.
ASKER
just some more info,
I am using the reference to Office 11, If I used a reference to Office 10 instead would that work, using the lowest Installed version?
I am using the reference to Office 11, If I used a reference to Office 10 instead would that work, using the lowest Installed version?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yep that totally worked.
Can I remove the COM reference, or do I still need it?
Can I remove the COM reference, or do I still need it?
yes if you are using late binding , you can remove com reference