[AccessD] VB.Net - seeing the messagebox

I am not sure whether this is true or not but I have always felt that I do
not have the same level of security issues that others might.  I am a one
man shop.  All of my systems run on a LAN behind a router.  No one routinely
remotes in to my system, I don't publish a web page (through the firewall
out to the web), I run software firewalls on all machines etc.

If I were going to take your advice, which I might, I would probably set up
one of my older machines as my personal workstation kind of machine.  With
everything on a single small lan, I actually use a kvm switch to switch
between up to 4 systems so it is simple to switch back and forth between
boxes.  I can also use remote desktop if I want to to get at each box.
Having Server 2003 running on the big boxes means I can actually have the
desktop showing on the monitor and remote in from my laptop (for example) to
another instance of the same user, or even another user.  Remote desktop
across a local LAN is just as fast as live.

John W. Colby
Colby Consulting
www.ColbyConsulting.com
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Francisco Tapia
Sent: Monday, May 14, 2007 1:15 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] VB.Net - seeing the messagebox

That is true John, but you ought to consider running your VS on an XP box to
help avoid other security issues from 2003.  2003 is an excellent OS and one
that we had not had many issues with, however I don't use this OS for
anything other than a strict Server OS.  That means nothing that is not
Server related, (Sql 2000/2005 only).

One thing you can consider is to install VMware Server (free copy) and use a
product like VMware Converter (also free) to create an XP OS on your server.
You can then install VS on there and run it on one of the cores for your 64
server.  (choose 1 instead of two so that you can allow the Sql server to
utilize as much CPU as needed for cpu intensive process.  Also place the
Virtual Disks on a disk not utilized by your sql server, I remember you had
segregated everything... even a Usb2.0 drive will help here, where you
install your vmware machine to that usb2.0 drive to help maintain
performance on the vmware machine and not take any away from your sql server
functions (such as those required for the high intensive reads, ie,
imports/exports).

my two cents (both the products I mentioned are provided free of charge from
Vmware)

--
Francisco