Getting Started

I over simplified a bit in my initial explanation. The website which already exists is a unix site. The application we are working on is to be an added feature.

My problem is that we need to somehow process data that resides in two different places: The client's data, and our data.

The client's already has servers in place and I assume will tell us how to access it.

As far as our data is concerned, I have two choices as I see it. 1) Move it to mySQL on the unix machine.(which will require periodic updating). 2) Figure out a way to keep it on our machine and access it from the unix site. It was option 2 that prompted my initial post.

Hope this is clearer...

Jim

----- Kristofer Gafvert wrote: -----

I'm not sure i understand. You say that you already are gonna use a unix
server, so where comes IIS in?

--
Regards,
Kristofer Gafvert - IIS MVP
<a style='text-decoration: underline;' href="http://www.ilopia.com" target="_blank">http://www.ilopia.com</a> - When you need help!


"Jim" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
news:6953D69F-19CC-413C-B059-4B6C7641C574@microsoft.com...
  > I need help understanding some really basic concepts.
   >> We're a small office that has hitherto developed Access applications that
crunch our client's data for them. So now they want an internet application.
   >> What do I have to do to make the Access data on a machine in our office
available for queries from a website form residing on a unix server
somewhere out there on the internet.
   >> The machines in the office are networked and running XP and are connected
to the internet via DSL. We want only one of them to be available onLine and
only to queries from a specific website.
   >> Am I correct in assuming:
  > 1) I need IIS
  > 2) I need a static IP but not necessarily a domain name. (But how does the
IP address get pointed to my machine.)
  > 3) I need a router to direct the request to the correct machine in the
office.
  > 4) The IIS that comes with XP Professional will be sufficient for
development but not so once the whole ball of wax is up and working.
  > 5) In the long run I'll probably drive myself crazy if I try and do it
myself and should probably hire someone who knows what's what.
  > 6) OR, It would probably be easier all around for me to just move our data
to mySQL and write some Perl scripts. At least the whole mess is in one
place and I wouldn't need to try and wrap my brain around all of this.
Although I'm more than willing to try if someone out there can jump start my
synapses.
   >> Thanks in advance for any help,
   >> Jim<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Getting Started 

Hi

a) You need a static *public* address. I assume you already have one - it's
assigned to your router. If you are using NAT to hide your internal
addresses (becuase they are not public), then your NAT device should be able
to do port-forwarding. Forward port 80 (for HTTP traffic) to your internal
webserver. Otherwise, if your internal addresses are public, you don't need
to do anything.

b) On IIS, the most common development platforms are ASP and ASP.NET. There
are lots of books available on developing ASP or ASP.NET applications. For
ASP.NET I recommend Stephen Walther's ASP.NET Unleashed:
www.adopenstatic.com/resources/books/ For Classic ASP (which is an older
technology), I'd recommend the Wrox Beginning ASP v3 and Professional ASP v3
(if you can still get hold of them).

Cheers
Ken

"Jim" <anonymous RemoveThis @discussions.microsoft.com> wrote in message
news:6953D69F-19CC-413C-B059-4B6C7641C574@microsoft.com...
: I need help understanding some really basic concepts.
:
: We're a small office that has hitherto developed Access applications that
crunch our client's data for them. So now they want an internet application.
:
: What do I have to do to make the Access data on a machine in our office
available for queries from a website form residing on a unix server
somewhere out there on the internet.
:
: The machines in the office are networked and running XP and are connected
to the internet via DSL. We want only one of them to be available onLine and
only to queries from a specific website.
:
: Am I correct in assuming:
: 1) I need IIS
: 2) I need a static IP but not necessarily a domain name. (But how does the
IP address get pointed to my machine.)
: 3) I need a router to direct the request to the correct machine in the
office.
: 4) The IIS that comes with XP Professional will be sufficient for
development but not so once the whole ball of wax is up and working.
: 5) In the long run I'll probably drive myself crazy if I try and do it
myself and should probably hire someone who knows what's what.
: 6) OR, It would probably be easier all around for me to just move our data
to mySQL and write some Perl scripts. At least the whole mess is in one
place and I wouldn't need to try and wrap my brain around all of this.
Although I'm more than willing to try if someone out there can jump start my
synapses.
:
: Thanks in advance for any help,
:
: Jim
 >> Stay informed about: Getting Started 

On Tue, 18 May 2004 19:36:04 -0700, Jim
<anonymous.DeleteThis@discussions.microsoft.com> wrote:

 >We're a small office that has hitherto developed Access applications that crunch our client's data for them. So now they want an internet application.
 >
 >What do I have to do to make the Access data on a machine in our office available for queries from a website form residing on a unix server somewhere out there on the internet.

Put your Access data on the web site. Though Access and IIS are
extremely poor choices for running on a Unix server. Especially since
IIS won't.

 >The machines in the office are networked and running XP and are connected to the internet via DSL. We want only one of them to be available onLine and only to queries from a specific website.

 >Am I correct in assuming:
 >1) I need IIS

You have IIS on XP Pro.

 >2) I need a static IP but not necessarily a domain name. (But how does the IP address get pointed to my machine.)

Your ISP assigns the sttc IP to your DSL connection. You rooute this
to your web server system through your router.

 >3) I need a router to direct the request to the correct machine in the office.

Yup.

 >4) The IIS that comes with XP Professional will be sufficient for development but not so once the whole ball of wax is up and working.

Can't tell. It's extremely limited, but no way to know whether you
can live within those limitations.

 >5) In the long run I'll probably drive myself crazy if I try and do it myself and should probably hire someone who knows what's what.

Or have site hosted elsewhere for you.

 >6) OR, It would probably be easier all around for me to just move our data to mySQL and write some Perl scripts. At least the whole mess is in one place and I wouldn't need to try and wrap my brain around all of this. Although I'm more than willing to try if someone out there can jump start my synapses.

If you know Perl and MySQL, then yes it would probably be a better
solution for you. You have to access from a Unix system, so using
Unix technologies would be cleanest and least prone to errors being
introduced.

Jeff<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Getting Started 

If you are not using IIS, then why are you asking on an IIS list?

If you are going to run Apache (for example) on the Unix box, why not ask in
an Apache group?

Cheers
Ken

"Jim" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
news:AAFDA7D5-8650-42ED-92CC-70412BA3C3DC@microsoft.com...
: I over simplified a bit in my initial explanation. The website which
already exists is a unix site. The application we are working on is to be an
added feature.
:
: My problem is that we need to somehow process data that resides in two
different places: The client's data, and our data.
:
: The client's already has servers in place and I assume will tell us how to
access it.
:
: As far as our data is concerned, I have two choices as I see it. 1) Move
it to mySQL on the unix machine.(which will require periodic updating). 2)
Figure out a way to keep it on our machine and access it from the unix site.
It was option 2 that prompted my initial post.
:
: Hope this is clearer...
:
: Jim
:
: ----- Kristofer Gafvert wrote: -----
:
: I'm not sure i understand. You say that you already are gonna use a
unix
: server, so where comes IIS in?
:
: --
: Regards,
: Kristofer Gafvert - IIS MVP
: http://www.ilopia.com - When you need help!
:
:
: "Jim" <anonymous.RemoveThis@discussions.microsoft.com> wrote in message
: news:6953D69F-19CC-413C-B059-4B6C7641C574@microsoft.com...
: > I need help understanding some really basic concepts.
: >> We're a small office that has hitherto developed Access
applications that
: crunch our client's data for them. So now they want an internet
application.
: >> What do I have to do to make the Access data on a machine in our
office
: available for queries from a website form residing on a unix server
: somewhere out there on the internet.
: >> The machines in the office are networked and running XP and are
connected
: to the internet via DSL. We want only one of them to be available
onLine and
: only to queries from a specific website.
: >> Am I correct in assuming:
: > 1) I need IIS
: > 2) I need a static IP but not necessarily a domain name. (But how
does the
: IP address get pointed to my machine.)
: > 3) I need a router to direct the request to the correct machine in
the
: office.
: > 4) The IIS that comes with XP Professional will be sufficient for
: development but not so once the whole ball of wax is up and working.
: > 5) In the long run I'll probably drive myself crazy if I try and do
it
: myself and should probably hire someone who knows what's what.
: > 6) OR, It would probably be easier all around for me to just move
our data
: to mySQL and write some Perl scripts. At least the whole mess is in
one
: place and I wouldn't need to try and wrap my brain around all of
this.
: Although I'm more than willing to try if someone out there can jump
start my
: synapses.
: >> Thanks in advance for any help,
: >> Jim
:
:
:
 >> Stay informed about: Getting Started