One question though - are the other .mdb files other than "amazing charts.mdb" (like codes, schedule, AmazingMeds) necessary to share? Are they changed in daily use, or just updated periodically? Do I want to get them out of that shared drive or does it matter?
Jim, I applaud your idea of only having the six databases in the shared database folder on your server. Of course, as soon as you have one imported item, that folder will reside there as well. The answer to your question is no matter how often they are updated ALL of them MUST be in the folder. If you remove any (and I am not sure why you would want to), you cannot run AC. It will simply give you an error message that the particular database removed is not accessible. Basically, with an Access Database, the tables are relating to each other, and do not play well together if any of their friends are missing.
Please don't take any of my comments or advice the wrong way. Just trying to help. Sometimes words on here don't translate as well. But, there is a reason the server threads quickly "degenerate" into techie gobbledy gook. It's important stuff and in order to get the most out of the wonderful program Jon has created, the networking needs to be done correctly.
We have a brand new server running Windows server 2003 R2 standard edition. Have a total of 10 PC's, including 5 in exam rooms, all running Windows XP Home edition (I know), hard-wired to our office network. I have a good IT guy helping me out. We have the D:/ drive on the server designated for data to make backups easy. We've mapped each of the client PC's to the D:/ drive on the server, so according to my IT guru, my Home OS should work fine.
It is good to know that your network is working using XP Home.
There are a few workarounds that do allow one to run XP Home on a domain network, although XP Home will not actually be on the demand. Your IT person has mapped the D:\ drive so that each client running XP Home can access the server each time most likely utilizing usernames and passwords located on the server. There is one very technical workaround that will even allow XP Home to function as XP Pro Lite so to speak and actually connect to a domain. But, for all practical purposes, XP Home unlike XP Pro can NOT connect to a domain. In other words, they can access files on the server as you are doing, but they will never be domain clients. This will mean they will not be able to utilize many of the functions and features of the server such as Active Directory, Policies, etc. This should be looked more so in reverse, i.e. your IT person will not be able to set certain global policies, etc.
While your IT person is telling you that your Home OS will work fine, I suppose it depends on what you consider fine. It just seems like ordering a hamburger and fries at a fine restaurant. You have a brand new server running what many would consider to be one of the best server OS available, yet you are using XP Home. XP Home is for home. Again, as I am only trying to help, but I would think you would be much better off upgrading the ten XP Homes to XP Pros. Most of the time computer users will do work arounds when they have an actual domain running XP Pro or Vista, etc. and have one or two Home OS to attach. Seeing that the home version can only run as a workgroup, they will never be on the domain.
I have no intention to ever use the server as a workstation or to run AC on the server. In fact, there's not even a monitor attached - I can access it and operate it through a VPN on my desktop PC, so there's little danger anyone would use it as a workstation.
This is very good. It is best practice to never use the server as a workstation.
Since I will never be using the server to run AC, can I simply do the full AC install to the server's C:\ drive, MOVE the data folder to the D:\ drive and then install AC on the clients? Or is it preferable to install the entire program to the D:\ drive on the server? Or just move a copy of the data folder from one of the clients on to the server's D:\ drive and not even fool with an install on the server?
Jim, this is completely up to the user. In theory, all of the above will work, and there are no huge particular advantages to any. You can install the program on the server hundreds of times; doesn't matter. As long as the six databases are somewhere that can be shared, and they are the ONLY ones shared. Let's look at all three individually. First, installing to the C: drive and moving the data to the D: drive works. I don't recommend this. First, the only reason you would be installing it would be to have the six databases you are going to move over. So, after moving the data, depending on whether you cut and paste or copy and paste, it is possible to have two sets of databases on the server. Although the C:\ drive's databases may not be shared, it is still asking for a problem down the road. I could be wrong, because there are many files in the AC folder, but the only one that I could see that would be helpful would be the userdic.tlx (dictionary file), but unfortunately, the dictionary files are used only on the individual clients. Although even this can be random at times. So, the only advantage to installing it there would be the ability to use it there, which as you have already pointed out, you don't want. Installing to the D:\ drive would accomplish everything you need. You could access the databases and have an application there you could run IF you wanted. For me, this would be the second best way to do it. Of course, for OCD people like me, I do not like anything other than data on the D:\ drive as you have pointed out for yours. So, now you have an application there that you are backing up every night. Yes, you can easily copy and paste the databases from any workstation and share it out, which is what I do. Just one other thought. While it isn't best practice to run the AC application from the server over the network this can be done by making shortcuts to the executable file on the server. You will be able to run AC just as if it were on your own desktop. Two huge disadvantages and probably more: Speed and the lack of ability for users to set up the AC application for them, logging in under his or her name, etc.
[quote-.]In any case, the installer asks at the start about whether the program is going to be shared from this computer, or not. I figured I should install on the server first since I was sharing from there, but does it really matter? What about the database tuning issue (I don't really even know what that is but it seems important) and any other future problems I don't even know enough to ask about.[/quote]
The installer asks that to help it with its initial path. You can disregard that as to how to set up your network. So, no, it doesn't matter. The database tuner will look for the databases that you are connected to. The database tuner updates the databases to work with any code changes made in the update you have just installed. These are generally "backwards compatible" so you can tune your databases and not upgrade every client. But, I can't promise this each time.
You can, if you wish, uninstall AC from the server now, and it shouldn't affect your databases. Of course, if you have any real data in them, you should back them up.
Thanks for your question. Basically, you can do it any of the ways you talked about, so I don't think I have been very helpful. But, I would consider upgrading to XP Pro so you can actually connect each computer to the domain giving you the ability to have usernames and passwords on each client so each user has to log into the server. This allows better security and auditing and, even better, allows users to use multiple computers having their own profiles and even use remote profiles if they wish.
I think I did degenerate a bit.
