Question 1 : Which database should I choose if I'm curretly working on a 

protype which requires a considerably large database

Question 2: What advantages ms Access database has over sql2000 database

Question 3: I don't quite understand this.When I download  as ASP page 

from the Internet, I don't actually need PWS(I'm running on Win 98), but 

why is that when I  design a ASP page I still need PWS.

Question 4: Is there a way I can let my supervisor see the advancement of 

my prototype through the Internet.

Hi,



> Question 1 : Which database should I choose if I'm curretly working on a

protype which requires a considerably large

> database



I would go with SQL Server...it can hold more records, the access time is

faster, overall performance is better, and it handles transactions better.

How "large" is large?  Access tables can hold a maximum of 65,000,000

records each.



> Question 2: What advantages ms Access database has over sql2000 database



By definition, Access is a desktop database application, while SQL Server is

an enterprise-level database application.  Both will work, but Access is

better if you're just getting started out.  MS Access is nearly everywhere,

being shipped with MS Office.  It's also far easier to setup and program

against.  SQL Server generally requires an understanding of T-SQL and has

more tight requirements (like having access to an NT 4 Server or Windows

2000 Server machine).



> Question 3: I don't quite understand this.When I download  as ASP page

from the Internet, I don't actually need PWS(I'm

> running on Win 98), but why is that when I  design a ASP page I still need

PWS.



When you download a page with .ASP as the file extension, it's doing

server-side processing off of some Web server located across the Internet.

These more often than not will be IIS 4 or IIS 5.  If you view ASP files

locally (on your own machine), you can use PWS, because largely only you

will be able to see the pages, and not over the Internet.



> Question 4: Is there a way I can let my supervisor see the advancement of

my prototype through the Internet.



There are 2 ways to do this with PWS.  (1) If you are both connected to the

same LAN, he can type in your machine's network name, and then the address

of the path to the file.  For example, if your machine is named

"testprojects", your ASP page's URL can be http://testprojects/mypage.asp ,

depending how you setup PWS.  (2) If you want to go all across the Internet

to let your supervisor see your work, and you can establish a dial-up connec

tion to the Internet, you can use the IP address dynamically assigned to

your machine when your dial-up as your machine's address.  So, if you

dial-up through an ISP and get "123.45.67.123", your URL could be

http://123.45.67.123/mypage.asp .  Of course, this will expire after your

connection is terminated to your ISP.  To find out what your IP address is

upon dialing-up, type in "winipcfg" (for Windows 95/98) in the Run menu box.





HTH,

Jason



----- Original Message -----

From: "Tan Chye Ting" <chyeting18@h...>

To: "ASPToday Discuss" <asptoday_discuss@p...>

Sent: Saturday, December 08, 2001 8:42 AM

Subject: [asptoday_discuss] ms Access vs sql2000





> Question 1 : Which database should I choose if I'm curretly working on a

> protype which requires a considerably large database

> Question 2: What advantages ms Access database has over sql2000 database

> Question 3: I don't quite understand this.When I download  as ASP page

> from the Internet, I don't actually need PWS(I'm running on Win 98), but

> why is that when I  design a ASP page I still need PWS.

> Question 4: Is there a way I can let my supervisor see the advancement of

> my prototype through the Internet.

>

Actually, the /development/ version of SQL Server 2000 does not require a 

server.  It will run on Windows NT workstation or Windows 2000 

Workstation.  It looks and acts the same as the regular version of SQL 

Server 2000, but has some limits regarding performance and allowed number 

of connections.  You can find out details at the MS web site.



One thing not mentioned by Jason was cost.  The database engine that 

Access uses is free to distribute with your application.  SQL Server is 

definitely not free.



If your application is going to use ASP and SQL Server 2000, you can use a 

single Windows NT/2000 Workstation machine with both PWS and the 

development version of SQL Server 2000.  Then, when you're ready to 

deploy, the ASP code will run without changes on a real web server (IIS on 

Windows NT/2000 Server) and the database can be copied without any changes 

to a real database server (SQL Server 2000 on Windows NT/2000 Server).  In 

fact, depending on the number of users that will be using your 

application, a single machine could be used to run both IIS and SQL Server 

2000.



Regards,

Greg