Can MicrosoftWord share the document?

K

Krich

I mean can Word share document like this. 2 person use
different computer access same document at the same time
and still can edit the document and can see the change
made by other user. Can MicrosoftWord doing something
like this?
 
C

Cindy Meister -WordMVP-

Hi Krich,

No, it cannot. Word 2003 via a Document Workspace on
Sharepoint can let more than one person work with the same
document, and then merge/compare their changes. But no way
to work absolutely simultaneously and see what the other
person is doing.

Although you can get something a bit similar with
NetMeeting, if you have a really fast network connection.
I mean can Word share document like this. 2 person use
different computer access same document at the same time
and still can edit the document and can see the change
made by other user. Can MicrosoftWord doing something
like this?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update
Jan 24 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any
follow question or reply in the newsgroup and not by e-mail
:)
 
L

Lars-Eric Gisslén

Helmut.

Not all true :)

Many database system relies an live data. I think Krich is thinking of
something smililar.

Regards,
Lars-Eric
 
L

Lars-Eric Gisslén

Cindy,

I really don't agree with you, unless I have missunderstood you. Locking a
record while editing may work in a small inhouse system but is normaly a no
no in large systems. I have never been involved in developing a DB system
locking a record while editing it. There are to many traps involved in that.

Regards,
Lars-Eric
 
L

Lars-Eric Gisslén

Cindy,

I guess you are right. I think you are much better than me on Office and I
may be better than you on pure system development. I've been a system
developer for about 17 years and been involved projects ranging from a few
weeks to system taking more than 20 work years to develop (like 4 years for
5 developers). Infact, nearly all systems I've been involved in has been DB
system in a way or another. We got into Office because we work with
digitally signed documents (instead of signed by a pen) and we use Office as
the document platform. Our latest project is to integrate our software with
the next version of BizTalk. This is quite fun and stimulating but writing
logic in VBA sometimes feels like a bigger challange than system
development, as the environment in Office is so much more unpredictable
compared to for instance API programming. For the moment we are fighting
with C# and Word 2003 (SmartDoc) and not using a single line of VBA code.
Even signing the documents are done from C# code. This has been very fun but
at the same time filled with a lot of head ache :)

Regards,
Lars-Eric
 
C

Cindy Meister -WordMVP-

Hi Lars-Eric,
I think you are much better than me on Office and I
may be better than you on pure system development.
This is quite fun and stimulating but writing
logic in VBA sometimes feels like a bigger challange than system
development, as the environment in Office is so much more unpredictable
compared to for instance API programming.
For the moment we are fighting
with C# and Word 2003 (SmartDoc) and not using a single line of VBA code.
Ah, now THAT I find interesting. How in heavens name can you do SmartDocs
without even a smidgen of Word VBA to manipulate the actual document?

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jan 24 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :)
 
L

Lars-Eric Gisslén

Cindy,

I hardly believe you need to go through VBA to access Words COM Interface.
Words COM interface is defined in MSWORD9.OLB (for Word 2000). As VBA is a
product integrated into Word and is not application specific in that way, I
would be very surprised if the calls goes through VBA. That would mean a
call to Word would go to VBA which in turn would call Word. That would be
very, very unefficient. VBA is actually a product that you can licence and
use in products that you develop by your self. If you take a look at this
site you might understand why I don't believe VBA is involved:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/office97/html/SF7BC.asp

As is states "Visual Basic in Microsoft Excel can access objects in other
applications that support OLE Automation, and in fact, Visual Basic uses OLE
Automation to call Microsoft Excel properties and methods" you may
understand why I have hard to believe the calls goes through VBA.

If you read the article above perhaps I can explain a few things. The 'vtbl'
is a short for Virtual Allocation Table, also often called V-table. It can
be treaded as list of function pointers. Using the vtbl is very fast as you
work directly with function pointers. If you use the IDispatch interface
your method name will be searched in the 'method table' (like a table of
contents) and from there get the function pointer. It's like when you want
to find a chapter in a book, if you use the vtbl you already know on which
page it is and goes directly to that page but with IDispatch you must first
look in the table of contents to find out on which page the chapter is and
then go to that page.

Regards,
Lars-Eric
 
J

Jonathan West

Hi Lars,

Technically you are quite correct. However, so much of understanding VBA
programming in Word is a matter of dealing with the Word object model that
Word VBA and the Word object model tend to be thought of as synonymous for
all practical purposes. For instance, most of the Word VBA Help file is
concerned with the objects methods & properties of the Word object model,
and very little by comparison is to do with the syntax of VBA itself.


--
Regards
Jonathan West - Word MVP
MultiLinker - Automated generation of hyperlinks in Word
Conversion to PDF & HTML
http://www.multilinker.com
 
L

Lars-Eric Gisslén

Jonathan,

Yes, but I think some basic understanding might sometimes be helpful. When
you use Word as an Automation Server (not unusual at all) you are actually
calling the same interface (object model) as VBA. So, if you can make your
business logic work in VBA you can port that code to your Automation Client
and get it working, just because both your Automation Client and VBA is
calling the same interface. That is not the same as the Automation Client is
calling VBA in Word.

The fact that your Automation Client will not be as fast as VBA is also
something that surprises many users, but that's the nature of mashalling
between different processes, and something you should be aware of. If the
equavalent VBA code works several times faster than your own code in the
client does not mean that your code is bad. It's someting you will have to
live with. :)

Regards,
Lars-Eric
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top