Win2000 Server and DB access
Posted on 2004-03-27
This seemed the best forum to ask this Win2kServer question, since it is a generic server question.
I admit ignorance about server and network issues - I am an out of date "single tier" programmer just learning new stuff. I have a large VB6 database application using ADO2.8 and Jet4.0 with an Access db running on a hospital network, the db is on a dedicated Win2k Server (nothing else on this server). The application has been accessing the db from each terminal by way of a mapped drive to the server db folder. Thus with ADO I have been addressing the db on the local mapped drive with a connection string like:
"Provider=Microsoft.Jet.OLEDB.4.0; Data Source=drive:\folder\dbname.mdb;Persist Security Info=False"
Problem is that the Win2k Server has a five license pack. We now need to run the application from 20 terminals. Mapping the server drive to 20 terminals requires 20 licenses (apparently-this is out of my area of knowledge), and seems pretty inefficient.
I know I can address the db by IP but have not done this with ADO. First question: How do I address the db, how does IS set the db up to receive the call. I supposed the address would be something like: Data Source=\\255.255.255.255\dbname.mdb;... Using the correct IP, that did not work when I was trying to test connection options. I am missing something in forming this address -- it is something simple, but I am uneducated. Please educate me.
Second question. Using an IP call to the server, there are unlikely to be 5 concurrent connections at any time. Connections always just grab data and close immediately. Assuming the win2k server license is setup properly, is there any problem with license issues having 20 different computers calling the server, as long as there are never more than 5 concurrent connections? I assume this is just fine, reading the MS license info.
This is pretty basic, but I need basic help. Thanks guys.