Datasets accross a network.

[tclancey]

Hi All.

I've been trying to think of a way to pass datasets, or tables from one PC
to another.

This would be the scenario.

Client PC sends an SQL query to a 'server'.
The 'server' would make a connection to a back end database.
The 'server' would retrieve data and send it back to the client.

It would basically be a way to avoid many PC's connecting to a back end
database.

I'm sure the way to handle the data transfer would be through sockets, but
how would I send a data table?

Any ideas?
Cheers,
Tull.

[Sachin Palewar]

If you don't need the n-tier model, then you can simply connect to
database on server directly from the client and when you have direct
access to database you can create datatable or do whatever you want
with the database. However if you want some kind of separate data
layer, then you should use a webservice on the server which will
serialise the dataset as XML and you need to deserialise it again on
client. .net remoting can also be a choice for you. I am not an expert
in any of these areas however.

You may like to check following article:
http://msdn2.microsoft.com/en-us/library/ms978496.aspx

Regards,

Sachin Palewar
(Certified Scrum Master)

Palewar Techno Solutions
(Mobile Solutions for Your Business)
www.palewar.com


On Mar 30, 10:22 pm, "tclancey" <[e-mail]:

Hi All.

I've been trying to think of a way to pass datasets, or tables from one PC
to another.

This would be the scenario.

Client PC sends an SQL query to a 'server'.
The 'server' would make a connection to a back end database.
The 'server' would retrieve data and send it back to the client.

It would basically be a way to avoid many PC's connecting to a back end
database.

I'm sure the way to handle the data transfer would be through sockets, but
how would I send a data table?

Any ideas?
Cheers,
Tull.

[tclancey]

Thanks for yout info, I'll take a look.
Cheers,
Tull.

"Sachin Palewar" <pa*****@gmail.comwrote in message
news:11**********************@o5g2000hsb.googlegro ups.com...

If you don't need the n-tier model, then you can simply connect to
database on server directly from the client and when you have direct
access to database you can create datatable or do whatever you want
with the database. However if you want some kind of separate data
layer, then you should use a webservice on the server which will
serialise the dataset as XML and you need to deserialise it again on
client. .net remoting can also be a choice for you. I am not an expert
in any of these areas however.

You may like to check following article:
http://msdn2.microsoft.com/en-us/library/ms978496.aspx

Regards,

Sachin Palewar
(Certified Scrum Master)

Palewar Techno Solutions
(Mobile Solutions for Your Business)
www.palewar.com


On Mar 30, 10:22 pm, "tclancey" <[e-mail]:

>Hi All.

I've been trying to think of a way to pass datasets, or tables from one
PC
to another.

This would be the scenario.

Client PC sends an SQL query to a 'server'.
The 'server' would make a connection to a back end database.
The 'server' would retrieve data and send it back to the client.

It would basically be a way to avoid many PC's connecting to a back end
database.

I'm sure the way to handle the data transfer would be through sockets,
but
how would I send a data table?

Any ideas?
Cheers,
Tull.

[Cor Ligthert [MVP]]

Tclancey,

A dataset is even at a standalone computer not such a fine thing comparting
with SQLExpress.
If it has an error mostly all your data is corrupted.

Secondly is a dataset not multiuser, only one user can work on it at a time.

Cor

"tclancey" <tu**@idcodeware.co.ukschreef in bericht
news:eX**************@TK2MSFTNGP02.phx.gbl...

Hi All.

I've been trying to think of a way to pass datasets, or tables from one PC
to another.

This would be the scenario.

Client PC sends an SQL query to a 'server'.
The 'server' would make a connection to a back end database.
The 'server' would retrieve data and send it back to the client.

It would basically be a way to avoid many PC's connecting to a back end
database.

I'm sure the way to handle the data transfer would be through sockets, but
how would I send a data table?

Any ideas?
Cheers,
Tull.

[Rad [Visual C# MVP]]

On Fri, 30 Mar 2007 18:22:10 +0100, tclancey wrote:

Hi All.

I've been trying to think of a way to pass datasets, or tables from one PC
to another.

This would be the scenario.

Client PC sends an SQL query to a 'server'.
The 'server' would make a connection to a back end database.
The 'server' would retrieve data and send it back to the client.

It would basically be a way to avoid many PC's connecting to a back end
database.

I'm sure the way to handle the data transfer would be through sockets, but
how would I send a data table?

Any ideas?
Cheers,
Tull.

Take a look at webservices. You could write one that retrieved the data
from a central server for applications to consume
--
Bits.Bytes
http://bytes.thinkersroom.com

[Rad [Visual C# MVP]]

On Fri, 30 Mar 2007 18:22:10 +0100, tclancey wrote:

Hi All.

I've been trying to think of a way to pass datasets, or tables from one PC
to another.

This would be the scenario.

Client PC sends an SQL query to a 'server'.
The 'server' would make a connection to a back end database.
The 'server' would retrieve data and send it back to the client.

It would basically be a way to avoid many PC's connecting to a back end
database.

I'm sure the way to handle the data transfer would be through sockets, but
how would I send a data table?

Any ideas?
Cheers,
Tull.

Take a look at webservices. You could write one that retrieved the data
from a central server for applications to consume
--
Bits.Bytes
http://bytes.thinkersroom.com