home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!uwm.edu!ogicse!news.u.washington.edu!hardy.u.washington.edu!someday
- From: someday@hardy.u.washington.edu (Scott Johnson)
- Newsgroups: comp.databases
- Subject: Re: Transferring traded-up Arev application to new system
- Message-ID: <1992Nov21.183939.9218@u.washington.edu>
- Date: 21 Nov 92 18:39:39 GMT
- Article-I.D.: u.1992Nov21.183939.9218
- References: <By2Htq.E64@nic.umass.edu>
- Sender: news@u.washington.edu (USENET News System)
- Organization: University of Washington, Seattle
- Lines: 32
-
- In article <By2Htq.E64@nic.umass.edu> dtodd@titan.ucc.umass.edu (David M. Todd) writes:
- >I'm traded up a ARev 1.16 application to 3.0 and now I am going to
- >install the application at a new site where they have just bought 3.0.
- >
- >I once saw a suggestion to move a complex application in the following
- >way:
- >
- >2) Replace the old arev.exe file with the arev.exe file from the new
- >system to put the new serial number (and network counter) in effect.
- >
- >Does this work? Can this be accomplished just by replacing this one
- >file?
- >
- >|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ David M. Todd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
- >|Department of Psychology, University of Massachusetts, Amherst, MA 01003 USA|
- >|Phone: 413/545-0158 ___ <DTodd@Titan.ucc.UMass.EDU> _____ Fax: 413/545-0996|
-
- This will work if you ensure three things:
-
- (1) The source and target systems are at *exactly* the same revision
- level, that is, don't mix a 3.0 system and 3.01 EXE, for instance.
-
- (2) You make absolutely sure that your customer's AREV.EXE file gets
- installed in the right place, and that it is a totally legal and
- registered copy that they have bought. Keep everything legit please!
-
- (3) GOTO (2).
-
- Scott Johnson
- Revelation Technologies, Inc.
- (disclaimer: points (2) and (3) above directly impact
- the continued health of my employer and my job!)
-