IS Access that bad?

[middletree]

I've only used SQL Server until this latest project, and the only option is
Access. I've read some things here about how Access just isn't as good as
SQL Server, and I agree, but other than scalability, what other things
should I look out for?

Please note there this is for a church, and perhaps as many as 750 rows wil
be in the db when it's all done. I assume this will be well under the
limits of Access 2000. What othe limitations are going to be an issue?

[Aaron Bertrand [MVP]]

http://www.aspfaq.com/2195

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/


"middletree" <mi********@htomail.com> wrote in message
news:#t**************@TK2MSFTNGP10.phx.gbl...

I've only used SQL Server until this latest project, and the only option is Access. I've read some things here about how Access just isn't as good as
SQL Server, and I agree, but other than scalability, what other things
should I look out for?

Please note there this is for a church, and perhaps as many as 750 rows wil be in the db when it's all done. I assume this will be well under the
limits of Access 2000. What othe limitations are going to be an issue?

[middletree]

Thanks, Aaron.
"Aaron Bertrand [MVP]" <aa***@TRASHaspfaq.com> wrote in message
news:#7**************@TK2MSFTNGP12.phx.gbl...

http://www.aspfaq.com/2195

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/


"middletree" <mi********@htomail.com> wrote in message
news:#t**************@TK2MSFTNGP10.phx.gbl...

I've only used SQL Server until this latest project, and the only option

is

Access. I've read some things here about how Access just isn't as good as SQL Server, and I agree, but other than scalability, what other things
should I look out for?

Please note there this is for a church, and perhaps as many as 750 rows

wil

be in the db when it's all done. I assume this will be well under the
limits of Access 2000. What othe limitations are going to be an issue?

[Jim Allensworth]

On Sun, 11 Jan 2004 19:01:56 -0600, "middletree"
<mi********@htomail.com> wrote:

I've only used SQL Server until this latest project, and the only option is
Access. I've read some things here about how Access just isn't as good as
SQL Server, and I agree, but other than scalability, what other things
should I look out for?

Please note there this is for a church, and perhaps as many as 750 rows wil
be in the db when it's all done. I assume this will be well under the
limits of Access 2000. What othe limitations are going to be an issue?

It so happens that I am looking at a database table with 237,998
records (rows). There are also more than 80 tables in the MDB. It
works quite well. This is in A97, so you should be allright ;-)

In the link provided by Aaron pay particular attention to the link
regarding an "interesting discussion" which is:
http://www.15seconds.com/Issue/010514.htm

Which, points to ...
http://www.learnasp.com/learn/rsfast-intro.asp

....and...

http://www.learnasp.com/learn/rsfast-lib.asp
Happy reading <g>

IOW, Jet can probably handle more than you realize.

- Jim