Re: Browser as Front-End
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Mon, 9 Jan 2006 22:34:56 +0000 (UTC)
Noam Nelke (NoamNelke@xxxxxxxxx) writes:
> I'm trying to build an app. for my parents' office. They have a small
> office (5 PCs), and they currently work with a very old program that's
> based on DOS. The program doesn't work well under XP, so they still use
> Win 98. They had their network upgraded about a year ago. They had
> Microsoft SBS 2000 installed, it includes SQL Server. I've written a
> few DB's in Access before, and now I'm just learning how to use SQL.
> Before I start work on their app., I have a question:
>
> I know it's possible to create an interface that can be put on their
> network and accessed via a browser. How is this done exactly?
That's a question that does not have much to do with SQL Server. Most
people seem to use ASP or ASP .Net. There is also Cold Fusion out there,
and probably a few more possibilities.
> It would be very beneficial for me, because it would mean that the new
> app. would be platform independent, so that they can upgrade to XP
> easily. It would also save us the cost of licensing front-end software
> (e.g. Access) for each machine.
On the other hand, browser-based interfaces are often painful to use.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- Browser as Front-End
- From: Noam Nelke
- Browser as Front-End
- Prev by Date: Re: Combining 3 SQL statements
- Next by Date: Re: Combining 3 SQL statements
- Previous by thread: Re: Browser as Front-End
- Next by thread: Maximum stored procedure, function, trigger, or view nesting level exceeded (limit 32)
- Index(es):
Relevant Pages
|
