Believe me, I do not insist on it

Post #52,396 by orion 9/19/02 8:35:06 PM Reply	Believe me, I do not insist on it I insist on alternatives to Wincrap. If it was up to me, I'd use Linux and Postgres SQL, and then use QMAIL for an email server, and then use SAMBA to let the Windows 98 workstations connect to the server. The Nurses won't know the difference as the program will still work the same, only a little faster and the server will not crash as much or need as much tweaking. Plus it would not cost as much for the server licensing. Plus we could wean them off Windows one at a time, and do it in Java with JBDC instead of VB and ADO with ODBC. As long as it looked the same, and generated the same reports, how are they going to know? They apparently cannot even tell the difference between "Missing Surigcal Tools" and "Unused Surgical Tools" in a tray, how the fck would they know the difference between a Windows 98 Client with a SQL Server backend and a Linux client running Java with a Postgres SQL backend running on another Linux machine with a local Postgres database for caching the local backups? [link\|http://games.speakeasy.net/data/files/khan.jpg\|"Khan!!!" -Kirk]*
Post #52,579 by mmoffitt 9/21/02 12:27:30 AM Reply	I might be smoking rope. I've said before I thought MS makes 2 decent products, one of the Sql Server. Have you looked at using MSDE (MS Sql Server engine limited to 5 "concurrent" users and FREE). Dunno if it fits your environment, but these little MSDE databases can be Replication databases. Just a thought... bcnu, Mikem
Post #52,646 by orion 9/21/02 6:41:49 PM Reply	Uh yeah Our average client has about 8 to 24 workstations, I assume that the limit of 5 would bite us in the ss later on. As soon as the 6th one goes to access the data, it will btch at them that it violated the server license. This of course, is not good. Thanks for the info, I might use SQL Server's Smaller Sister in a different project, maybe somewhere else? *[link\|http://games.speakeasy.net/data/files/khan.jpg\|"Khan!!!" -Kirk]*
Post #52,941 by mmoffitt 9/23/02 11:23:49 PM Reply	Depends on how you write it. If you use MTS, then the COM object talking to the server counts as 1 connection. Even if you open/close connections at the client, you might get away with it. My own preference is nobody has base table access, sp's for insert/update/delete/anything else done a lot, views for everything else. COM DB components to interface w/all client UI's. Doing that cuts down significantly on "concurrent connections" unless you use the same system for DSS. I've deployed MSDE in a small shop w/12 workstations (it's an office doing lots of edits) and never exceeded the 5 concurrent limitation. Just my 2, Mikem

Welcome to IWETHEY!