Jen,
Geoff and Ben are completely correct. I hate to throw a monkey wrench into all this, but it is hard to follow your posts. It sounds like you have a "pseudoserver" (I use that term to delineate between an "actual" server which runs Server software such as Windows Server 2003 or 2008 or SBS and a computer in a P2P that users use for running apps such as AC or billing software.
In one of your posts, you talk about having Windows 2000 on a regular PC that you are using as a pseudoserver. First, while you can use XP to access 2000, I wouldn't. It is much easier network-wise to use XP Pro as your "server" software. Make sure you use all XP Pro.
Then what SCARES me is your comment that you threw SBS 2003 on that computer. While SBS 2003 can run on any computer, I doubt the computer has the specs to run it efficiently, hence the slowness. Running SBS 2003 on a plain workstaion is kind of like putting a 350 HP engine on a bicycle.
In order to network properly, one has to decide what am I trying to accomplish. Am I looking for a really top notch client/server set up with SBS 2003 (excellent choice) on a "real" server with all XP Pro clients or Vista Business? Or, am I going to run P2P, which is fine (and can be run on a "real" server, but could easily be run on a workstation that has a good hardware setup (at least 1GB of RAM and a decent processor).
There should be no issues with adding data to AC. If AC works well on day one on the database, then it should be fine on day 300.
I am also confused as to not putting your old billing data on the server. I may be missing something, but everything should be on the server and not on external drives. (except for backups).
You mentioned earlier that your IT guy doesn't do servers. THEN HE ISN'T AN IT GUY. He is someone who knows a lot about computers. You can't set up a network which, by definition, is a group of computers who can all access files and applications from a single server be it P2P or client/server on a domain. To set up a network properly, the IT person needs to know how to set up the server.
When I read a thread like this, I try to determine if the author of the thread simply needs some direction or more help. Please don't take this the wrong way, but if you purchased SBS 2003, you will need some help installing it on a server.
Spend the money on the right equipment, get a server or pseudoserver that can run everything and DEFINITELY get an IT person to help. And with SBS, I would get a real server. You can get a good HP one for $1500 or so. I know that is a bit of money, but you will need it to run SBS correctly.
A word about IT people. Here is an analogy. Saying an IT person is like saying a doctor. By saying doctor are you talking about somene who just graduated medical school? Or someone who is completely licensed and board-certified in something. If my patient has JRA, I send them to a pediatric rheumatologist. If I need help with my network, I hire someone who is CERTIFIED to do this. Such as a Microsoft Small Business Certified IT person.
Again, as in other posts, sit down and design your network. Determine what you want such as P2P or client/server. Are you going to use Active Director in a domain setup, which you should if you use SBS 2003 or not? Once you decide what you want, then learn how to do it or hire someone who does.
