Exchanging data over the internet

Hi All,
In a couple of weeks, after finishing my current project, I'll start a -for
me- quite challenging project, so I'm already starting to do some research.
Since I had a little bump in with Aaron some time ago, when I asked for an
easiest solution, I'll just ask for some pointers this time ;-)
There are 2 companies involved. One is a school. The other one does the
examination of the school's students. On both ends, the software will be
developed in VB .NET, with -for starters- MSDE as the datastore. When a
student starts a course, his/her data will be entered in the school's
database. This data has to be send to the examination institute. After the
student has taken an exam, the results have to be send back to the school.
On both ends, they need their own database, since only part of the data will
be shared among the companies. As I said, they will both be running MSDE
2000 and they are both connected to the internet through DSL (with fixed
IP-adresses).
All pointers to exchange data this way are welcome. I'm not new to SQL
Server/MSDE, but still bit of a novice. I've read something about the
'famous' port 1433. But as far as I've understood opening that one might not
be a good idea, security-wise. I've also read something about webservices
(or something like that).
I'm quite stuck here. Please help me out a bit.
Thanks,
Willem
I would tier your system and create a .Net web service on both ends to send
and consume data. Creating web services in .Net is rather easy and VS .Net
comes with some sample projects to start from.
Jim
"Willem van den Broek" <willem@.chsd.nl> wrote in message
news:%23qamZc8NEHA.268@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> In a couple of weeks, after finishing my current project, I'll start
a -for
> me- quite challenging project, so I'm already starting to do some
research.
> Since I had a little bump in with Aaron some time ago, when I asked for an
> easiest solution, I'll just ask for some pointers this time ;-)
> There are 2 companies involved. One is a school. The other one does the
> examination of the school's students. On both ends, the software will be
> developed in VB .NET, with -for starters- MSDE as the datastore. When a
> student starts a course, his/her data will be entered in the school's
> database. This data has to be send to the examination institute. After the
> student has taken an exam, the results have to be send back to the school.
> On both ends, they need their own database, since only part of the data
will
> be shared among the companies. As I said, they will both be running MSDE
> 2000 and they are both connected to the internet through DSL (with fixed
> IP-adresses).
> All pointers to exchange data this way are welcome. I'm not new to SQL
> Server/MSDE, but still bit of a novice. I've read something about the
> 'famous' port 1433. But as far as I've understood opening that one might
not
> be a good idea, security-wise. I've also read something about webservices
> (or something like that).
> I'm quite stuck here. Please help me out a bit.
> Thanks,
> Willem
>
|||Thanks Jim. I was already afraid that would be the answer. I was hoping
there would be a solution without having to use IIS...
Willem
"J Young" <thorium48@.hotmail.com> schreef in bericht
news:OK2HMi9NEHA.3012@.tk2msftngp13.phx.gbl...
> I would tier your system and create a .Net web service on both ends to
send[vbcol=seagreen]
> and consume data. Creating web services in .Net is rather easy and VS .Net
> comes with some sample projects to start from.
> Jim
> "Willem van den Broek" <willem@.chsd.nl> wrote in message
> news:%23qamZc8NEHA.268@.TK2MSFTNGP11.phx.gbl...
> a -for
> research.
an[vbcol=seagreen]
the[vbcol=seagreen]
school.[vbcol=seagreen]
> will
> not
webservices
>