Griffiths, Richard
R.Griffiths at bury.gov.uk
Tue Apr 1 07:37:16 CST 2003
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 > -----Original Message----- > From: Jim Lawrence (AccessD) [SMTP:accessd at shaw.ca] > Sent: 01 April 2003 13:21 > To: accessd at databaseadvisors.com > 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: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Griffiths, > Richard > Sent: Tuesday, April 01, 2003 1:17 AM > To: 'AccessD at databaseadvisors.com' > 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 > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com -------------------------------------------------------------------------------------------------------------------- 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.