Gina Whipp said:
All,
My OTHER machine has finally bit the dust. And I have never tried this so
before I do... Can I load my SQL Server 2000 on the same machine as my
Access programs OR do I bit the bullet and get another machine?
We often do this. In fact, most of us develop this way. And, now that sql
server 2005 express edition is free, then this a really the preferred way to
develop. Keep in mind you in some cases will have to setup a loopback
connection if you computer has no network connection at all.
But, for the most part this is common setup. I believe the only Restriction
is that sql serer 2000 might not install on the home edition of winand dows,
but even then, I not sure that's the case.
Another common setup by used for testing and development for things like sql
server, SharePoint and web stuff that to be used with ms-access is to use
virtual PC. virtual PC lets you run several virtual machines on your
computer, so if you want to setup a server machine and then have two more
computers networked to that server, you can do this in the virtual world.
This is great because you don't have to purchase any hardware. You can build
imaginary networks and servers right on your own computer without having to
buy any new hardware at all. For testing of your software applications, and
testing of any installation routine to use for client computers, this is a
must have technology.
I run virtual PC all day on my laptop. When testing my installing scripts
for my access applications, I need a clean box that I can use for testing
over and over. Once you've done a test install of a program on a machine,
that machines never goes back to the way it was before when you actually
un-install the software. There is always bits and pieces and all kinds of
things left behind. with virtual PCs to test and install, you can throw the
machine away, and say give me a fresh new copy of windows and start from
scratch again (you don't even bother to uninstall software, you just tell
the virtual PC to throw away any changes made and give me a fresh new copy
of windows).
Keep in mind it's the absolute of no use to install and test your software
on your development machine because you been installing bits and pieces and
updates and libraries for the last five years. You can rest assured that any
application that you're working on will function correctly on your dev
machine. When it comes time to testing for deployment to other machines
(like your clients), you then need a pure clean up virgin untouched machine
with a clean fresh copy of windows.
People also often use virtual PC to set up a copy of their web server, or
even SQL server can be run and setup to run on virtual pc. I have an image
setup for SharePoint because I did not want to spend the money and time to
build a whole separate box just to test some SharePoint stuff. So I just put
setup windows 2003 as a virtual machine and installed SharePoint into that.
(and, I do this all on my laptop).
So consider virtual PC as a possible option here.
All in all virtual PC is really a must have development tool for any
developer out there, I highly recommend it and it's free from Microsoft.
http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx
