Client Server

[casox]

I know this may be a big question with a alot of answers. If someone can be brief in giving some direction it would be greatly appreciated. I've developed lots of stand alone databases but never anything on client/server. Essentially, what is the difference when coding a server database versus development for a standalone machine?

Thanks,

casox

[J Staniforth]

You may find writing a database in Access over a network as a convenient step.
This requires virtually no new concepts - you may get conflicts where two people independently modify the same record at same time. The reason being that it is not client/server. All the db is transmitted accross the network onto the client machines.
This obviously means a lot of potential network traffic and the need for suitably powerful client machines.
A c/s database is one where the server db lives on a main server machine accessed by several client db's. These send queries and retrieve the smaller subset of records that the client requires. An example of a c/s capable dbms is SQLserver.
Obviously doing this throws up a whole host of new issues which need to be dealt with.
Hope this is useful.
Regards,
John.