networking and office 2007

  • Thread starter Thread starter Jonsey
  • Start date Start date
J

Jonsey

Can I access Office 2007 through my home network.

My preference would have been to reinstall it on my new and now main
computer rather than accessing it on my old one, but, I do not have the
installation disc , only the product key

If I can still use it through the network that mught be less messy

Can anyone please help
 
You cannot run Access (or any other Office product) from an executable
installed on another machine. Access (and all other Office products) must be
installed on the local client machine.
 
But you can remote into another machine (terminal services or RDP) and then
you are actually using it on that machine. Perhaps not what he had in mind,
but it is the only way it will work.
 
You cannot run Access (or any other Office product) from an
executable installed on another machine. Access (and all other
Office products) must be installed on the local client machine.
Click to expand...

They need to be installed, but the application files don't need to
be stored on a volume internal to the machine on which they are
running. It makes little sense to run your app across the network,
but it's possible to do.

I mean, that was the way they used to deploy apps on Novell all the
time. I never understood why given that it made sense only for
diskless workstations, which I never encountered in that
configuration.
 
I mean, that was the way they used to deploy apps on Novell all the
time. I never understood why given that it made sense only for
diskless workstations, which I never encountered in that
configuration.
Click to expand...

Years ago I was a Novell admin (before I saw the light with NT). The
conventional "wisdom" of doing that was to keep track of license uses. In
those days a license for Word or Excel was about $250 each and there wasn't
any bundling into a suite like Office until Office 4.3 (or maybe 4.1, I
don't remember) In any case, even as late as Novell 4.0 admins were running
off of a server to minimize license use. That way they could buy 10 licenses
for as many as 15 or 16 users and install them per use, instead of per seat.

Later, when Office was bundled, it was much cheaper to run locally, and as
you say, made much more sense.
 
Years ago I was a Novell admin (before I saw the light with NT).
The conventional "wisdom" of doing that was to keep track of
license uses. In those days a license for Word or Excel was about
$250 each and there wasn't any bundling into a suite like Office
until Office 4.3 (or maybe 4.1, I don't remember) In any case,
even as late as Novell 4.0 admins were running off of a server to
minimize license use. That way they could buy 10 licenses for as
many as 15 or 16 users and install them per use, instead of per
seat.

Later, when Office was bundled, it was much cheaper to run
locally, and as you say, made much more sense.
Click to expand...

I never saw Novell until I went freelance in late 1994. By that
time, the Office suites were ubiquitous, so the justification for it
was already vanishing for most of these users.

And umpty-eleven mapped drives was something I kept seeing for a
long time, and the Novell-trained techs adapted the same stupidity
when they moved to NT-based servers (in the NT 4 time frame). I kept
telling them this made no sense, but I was the lowly workstation
tech, so I didn't know anything.

This is one of the reasons I was an early adapter of pure UNC paths
and shortcuts (populating Network Neighborhood and All Users
deskstop with standard shortcuts, for instance) without any mapped
drives. We're talking 1997 for the first client I got to have a say
in planning this.

Of course, it's no good to implement that if the server shares
aren't rationally organized, which means not mapping root to your
data drive (which is something I still see to this day).
 
Back
Top