VB - Access

[zambian]

I am developing a database with access using VB. It is currently on a single PC.

The next stage is to put it on a server. How do I do that and connect to it ?

The maximun number of clients at anytime on it will not be more than 11. Should I shift to SQL Server ?

[smalig]

You could place your database to the shared network device (for example, "Q:\database\db1.mdb") or you could use the UNC name like "\\Workstation1\database\db1.mdb".

------------------
smalig
[email protected]
http://vbcode.webhostme.com/

[VorTechS]

Whenever using a multi-user environment, if you have a large database and a large number of users moving to SQL Server is a definately good move.

MS Access databases are notorious for corruption under a multi-user environment, and eventually the corruption will get to the point where it is irrecoverable.

If you decide to move to SQL Server, go to SQL Server 7.0 as it's fairly straight forward to maintain (as it's almost self-maintaining). Also if you start to use procedures and triggers (which are superiorly faster than running queries) moving them from SQL Server 6.5 to 7.0 is very difficult (as I know many companies who have had major problems doing just that!)

[JohnAtWork]

If you're going to stick with Access, however, I would suggest looking at the Add-In Database Splitter.

Tools --> Addins --> Database Splitter

This will allow you to distribute a front-end database to all the parties involved.
I would also suggest implementing some sort of version control.

What I do is have two tables residing in the Front End, one linked to the backend, one local. They contain the version numbers.

When the main form loads, it verifies that these are both the same, and if not, it prompts the user to download the new version. (I have an application that copies the new file into their machine)

If you're interested, I could post the code here.