Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!rice!uw-beaver!cornell!vax5.cit.cornell.edu!ie3y
From: ie3y@vax5.cit.cornell.edu (Andy Swanson)
Newsgroups: comp.sys.mac.misc
Subject: <None>
Message-ID: <1990Dec20.151718.1731@vax5.cit.cornell.edu>
Date: 20 Dec 90 19:17:17 GMT
References: <49942@cornell.UUCP>
Distribution: world,comp
Lines: 24

In article <49942@cornell.UUCP>,
wayner@cello.cs.cornell.edu (Peter Wayner) writes:
> I've gotten plenty of mail about this and EVERYONE has been quite
> positive about their experience with MacWarehouse. I assume it
> is a fluke, although a bit of a pain.
>
> This leads to the question, "How do you design networked database
> software so that databases are kept consistent?" Why don't people
> do this? The airlines can do it, why can't the software developers
> who coded up the stuff for MacWarehouse.
>
>
> Peter Wayner   Department of Computer Science Cornell Univ. Ithaca, NY 14850
> EMail:wayner@cs.cornell.edu    Office: 607-255-9202 or 255-1008
> Home: 116 Oak Ave, Ithaca, NY 14850  Phone: 607-277-6678
     A minor suggestion on this.  In my experience,  you are generally given
  an order number.   Also,  your sales rep. will usually identify her/him self
  If you have a complaint,  use this information.  Call up MacWarehouse,
  (Or where ever you placed the order)  ask to speak to a manager, and give
  this information and your complaint to the manager.  Possibly even write
  a letter.  This will help to insure that this kind of thing doesn't
  happen in the future.

  +Andy Swanson