[AccessD] VB.Net - seeing the messagebox

I was also wondering this.

I have a desktop at home running 2000 Server...that has been running 24/7 
for over 3 years.  Every 30 minutes it retrieves stock data files(via 
FTP),unzips them, imports into Access, analyzes the data, does historical 
comparison, then emails the data to a number of phones(if anything matches 
criteria).

This is the only thing thing this box does aside from some periodic 
development...and the only problems I have had was 1 hard drive 
failure...and my email crashed...Neither an OS problem...other than 
that...this thing has never had an issue.

By no means am I an expert on OS's...but of the 15 or so machines I've had, 
running Win95,Win98,Win2000,Win ME(it came on the machine, not my 
choice),and XP.....2000Server has been the most stable machine I have ever 
had.

Just curious,

Mark A. Matte




>From: Jim Lawrence <accessd at shaw.ca>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "'Access Developers discussion and problem 
>solving'"<accessd at databaseadvisors.com>
>Subject: Re: [AccessD] VB.Net - seeing the messagebox
>Date: Mon, 14 May 2007 09:47:16 -0700
>
>Hi Gustav:
>
>Why is having a server as a desktop not a good idea? These are the reasons 
>I
>would recommend it:
>
>1. It runs more stably. Rarely crashes and I do put it through its paces. 
>XP
>on the other hand can freeze up easily when pushed too hard.
>2. Has great built-in security. It can not even be seen on the LAN if that
>is your requirement.
>3. Full admin terminal services built not just a single user. You can 
>easily
>remote in from a clients site.
>4. Easy communications with remote/local and different OS like Mac/Linux...
>try that with an XP box without a lot of fuss.
>5. Runs multiple resource heavy apps without grinding to a halt or just
>crashing: like a couple of web servers, a couple of SQL servers 2000/2005,
>virtual server and throw in a resource hungry graphic program. Try running
>Oracle Enterprise 10g on an XP box.... yeh-right.
>6. Runs multi-versions of development apps, like Access, VB, Visual
>Studio...
>7. For all these heavy duty programs the system can actually take full
>advantage of the entire RAM that can be crammed in the box. XP will look at
>the memory but will not necessarily do anything with it.
>
>I do not recommend this much load but for you multi-tasking power 
>users...my
>recommendation is if you have the opportunity is to run a nice Windows 2003
>standard server. It has a lot more complexity than the standard desktop and
>will not always play nice with other servers on the LAN but has all the
>tools to taming it.  ...After all many Linux distros have the capabilities
>of being full-blown, multi-user, multi-tasking servers with a pretty
>interface.
>
>Jim
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock
>Sent: Monday, May 14, 2007 1:01 AM
>To: accessd at databaseadvisors.com
>Subject: Re: [AccessD] VB.Net - seeing the messagebox
>
>Hi John
>
>A server OS for desktop use? Not a good idea.
>Perhaps your programs miss priority? Look up My Computer, Properties,
>Advanced, Performance, Settings, Advanced.
>
>/gustav
>
> >>> jwcolby at colbyconsulting.com 14-05-2007 04:07 >>>
> >No he's using VISTA....Heheheheheh.
>
>Nope, Windows 2003 Standard Edition.  Essentially XP on steroids I think.
>
>
>
>--
>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

_________________________________________________________________
PC Magazine’s 2007 editors’ choice for best Web mail—award-winning Windows 
Live Hotmail. 
http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_pcmag_0507