<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body>
Have a look at this Word doc article<br>
Office 97 to Microsoft Office XP Migration Issues<br>
Way at the bottom is discussion articles on large scale deployment<br>
Somethings discussed are changes to object module, late binding for office
automation and<br>
known problems with virus checkers.<br>
<a class="moz-txt-link-freetext" href="http://www.microsoft.com/office/ork/xp/journ/Xpdelta.htm">http://www.microsoft.com/office/ork/xp/journ/Xpdelta.htm</a><br>
<br>
Griffiths, Richard wrote:<br>
<blockquote type="cite"
cite="mid52339DF8DCA2A544AF660C8217EB7DCD0227F127@mailgate.bury.gov.uk">
<pre wrap="">Jim
thanks for that - I work for local governent so the number of pc's is say
about 5000 - we do use an image for installations - my input is not here
though, its to suggest how the various users some of which have been
upgraded and some who have not been upgraded can use their current access
applications. If think if we can have both A97 and Access XP installed is
best but this will depend upon whether the Access 97 lisences have been used
for the XP ones
Richard
</pre>
<blockquote type="cite">
<pre wrap="">-----Original Message-----
From: Jim Lawrence (AccessD) [<a class="moz-txt-link-freetext" href="SMTP:accessd@shaw.ca">SMTP:accessd@shaw.ca</a>]
Sent: 01 April 2003 13:21
To: <a class="moz-txt-link-abbreviated" href="mailto:accessd@databaseadvisors.com">accessd@databaseadvisors.com</a>
Subject: RE: [AccessD] A97 - AXP
Hi Richard:
Unless there are a large amount of computers in the office. Access97 and
Access2000 will have to be installed, individually on each computer
requiring access to the specific versions of Access. It can be a slow
process. If you are responsible, for such an event, you may want to start
trying to move the users up to one version of Access, like XP. I have
found
that most applications will upgrade without issue. This will take a high
degree of tack, may require some training sessions and therapy for
yourself.
In a larger office, when a big roll-outs it is done, it is more economic,
to
replace all the computers with a standard model, create a standard CD OS
image or server image. This image can have all three versions, A97, A2K
and
AXP setup. All custom applications will have to run off the server(s). In
this scenario, after the initial station is fully tested, the image is
generated from that station, then each computer can be upgraded in about
ten
minutes. You should only entertain this idea if there were more than
thirty
computers to upgrade.
You can run all three versions of Access on the same box, just work
backward
from the current version to the oldest, making sure you do not over-write
any directories or files. I would recommend trying to wean everyone off
older versions, assuming all the applications have their source code.
(With all the individuals creating and running their own applications, in
every version of Access, it sound like my worse nightmare...At least you
have job security. Then proper license issues can be really ugly... If
there
are enough people, a site-license can be a cheaper alternative.)
HTH
Jim
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:accessd-bounces@databaseadvisors.com">accessd-bounces@databaseadvisors.com</a>
[<a class="moz-txt-link-freetext" href="mailto:accessd-bounces@databaseadvisors.com">mailto:accessd-bounces@databaseadvisors.com</a>]On Behalf Of Griffiths,
Richard
Sent: Tuesday, April 01, 2003 1:17 AM
To: '<a class="moz-txt-link-abbreviated" href="mailto:AccessD@databaseadvisors.com">AccessD@databaseadvisors.com</a>'
Subject: [AccessD] A97 - AXP
Hi
looking for advice.....we are currently rolling out XP with office XP.
Most users beforehand used A97 (a few A2000, A95). I have been asked to
suggest way forward w.r.t. how to implement this process w.r.t to users
still being able to run their existing access applications.
In summary
some applications are user developed using direct access to tables ie.
table
view
some applications third party developed
most still have A97
some have been upgraded to XP
My initial thoughts were to wrap up all the A97 apps into runtime and
distribute......
however this has problems as users have designed some of their apps using
table views etc which do not work under runtime
also this option prevents users from going in and setting up their own
queries and making their own amendments i.e. using full blown Access.
So how can A97 users run along side AXP (A2000) users most efficiently?
Can
this be done??
(I did think whether users should keep hold of their A97 copy in addition
to
Office/Access XP, but I think we may have used those licenses for the
upgrade to Office XP)
Any experience/suggestion would be greatly appreciated.
Richard
--------------------------------------------------------------------------
--
----------------------------------------
This e-mail, together with any files transmitted with it, is
confidential and intended solely for the use of the individual to
whom it is addressed. If you are not the intended recipient, or
the person responsible for delivering to the intended recipient,
be advised that you have received this e-mail in error and that any
use, dissemination, forwarding, printing or copying of this e-mail
is strictly prohibited without liability on our part.
By responding to this e-mail it is accepted that your response
may be the subject of recording/monitoring to ensure compliance
with the Council's ICT Security Policy
If you have received this e-mail in error please notify the sender.
_______________________________________________
AccessD mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AccessD@databaseadvisors.com">AccessD@databaseadvisors.com</a>
<a class="moz-txt-link-freetext" href="http://databaseadvisors.com/mailman/listinfo/accessd">http://databaseadvisors.com/mailman/listinfo/accessd</a>
Website: <a class="moz-txt-link-freetext" href="http://www.databaseadvisors.com">http://www.databaseadvisors.com</a>
_______________________________________________
AccessD mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AccessD@databaseadvisors.com">AccessD@databaseadvisors.com</a>
<a class="moz-txt-link-freetext" href="http://databaseadvisors.com/mailman/listinfo/accessd">http://databaseadvisors.com/mailman/listinfo/accessd</a>
Website: <a class="moz-txt-link-freetext" href="http://www.databaseadvisors.com">http://www.databaseadvisors.com</a>
</pre>
</blockquote>
<pre wrap=""><!---->--------------------------------------------------------------------------------------------------------------------
This e-mail, together with any files transmitted with it, is
confidential and intended solely for the use of the individual to
whom it is addressed. If you are not the intended recipient, or
the person responsible for delivering to the intended recipient,
be advised that you have received this e-mail in error and that any
use, dissemination, forwarding, printing or copying of this e-mail
is strictly prohibited without liability on our part.
By responding to this e-mail it is accepted that your response
may be the subject of recording/monitoring to ensure compliance
with the Council’s ICT Security Policy
If you have received this e-mail in error please notify the sender.
_______________________________________________
AccessD mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AccessD@databaseadvisors.com">AccessD@databaseadvisors.com</a>
<a class="moz-txt-link-freetext" href="http://databaseadvisors.com/mailman/listinfo/accessd">http://databaseadvisors.com/mailman/listinfo/accessd</a>
Website: <a class="moz-txt-link-freetext" href="http://www.databaseadvisors.com">http://www.databaseadvisors.com</a>
</pre>
</blockquote>
<br>
</body>
</html>