Basics for "client"-server operation

Greetings. We have a client who wants to develop a mission-critical application using remote PC's connecting via dial-up to a central server. Given that the eventual number of PC's dialing in will approach 300, and that the server strategy suggests a Sun, Informix is leading Sybase and Oracle in preference purely due to the cost of _unlimited_ licensing. However, the desire of our customer is to build the client application using FoxPro, about which we know nothing. Also, they "have been told" that they can purchase SQL-server (Sybase) running under Windows-NT (also, about which we know nothing) for $5000.00 for an unlimited number of users. Now, the questions: 1) An unlimited license (>96 users) for Sybase is priced at $92,000. What is SQL-server leaving out to be priced at $5,000? 2) If we go with Informix (OnLine 5.x), how do we connect the FoxPro clients? The modems will be connected to terminal servers, connected to the Sun. I've been told that we _must_ use I-Star and I-Net/PC even though the connects will be through dial-ups. I _really_ don't want to have to run PPP or SLIP if I don't have to. Also, the customer is concerned about being nickel'd and dime'd by Informix when he can "get everything in one package" via the SQL-Server/NT route. 3) I'm very nervous about my customers being on the "b"leeding edge and don't feel NT has a sufficient track record (and yes, I qualify as a UNIX bigot). Does anyone have experience with a successful project using NT/SQL-Server. My preference would be to use Informix, but if the customer doesn't feel good about the price-point or is overwhelmed by the "complexity" of hooking it all together, and SQL-server gives him warm fuzzies, I can't make a case. Thanks in advance for your input. John Bossert bossert@thalatta.com