users and adp

[ciroteo]

I would like to start a new application which should be used more or less by
250 users simultaneously.
Should I try adp's with some version of sql 2005 or should I put all on asp
application?
I haven't still understood which kind of version are in the new sql, are
there any limitations in the number of users?

 

[dbahooker]

you should probably try ASP.net.. Dreamweaver is an awesome tool for
developing simple websites using templates / wizards.

ADP is a great platform.. there is not a limit on the number of users.
MDB can't scale to a dozen users reliably.

It's entirely possible that moving to ADP would give excellent
performance.. but I would make sure that you have a pretty beefy Server
to run the database side.

-Aaron

 

[dbahooker]

btw, are you using SQL 2005 Express???

SQL 2005 is going to work great with Access 2007.. you should be able
to buidl a solution in Access 2007 and then distribute it to Access
2003 users; from what I heard it is 'binary-compatabile' with Access
2003.

-Aaron

 

[ciroteo]

(e-mail address removed) ha scritto:

btw, are you using SQL 2005 Express???

SQL 2005 is going to work great with Access 2007.. you should be able
to buidl a solution in Access 2007 and then distribute it to Access
2003 users; from what I heard it is 'binary-compatabile' with Access
2003.

-Aaron

thank you. last year i bought the acc2003 developer version, so i would
like to stay on this platform for a while. I know that there's a big
debate on the future of adp, but I hope that things will change. Even
if somebody in Microsoft suggest to connect by odbc I think that is
more important to let developers improving skills (from mdb) using the
strenght of stored procedures and other stuff in native way on adp/sql
server.

 

[Sylvain Lafontaine]

The number of simultaneous users doesn't really matter for the decision of
using either ADP or ASP.NET, both or them or none of them and insteand, you
will to take into other factors like the location of your users (LAN,
INTERNET, Firewall, Proxy, etc.) and what you want to do this database.

With 250 users at hand, I would suggest that you consult someone with the
required expertise.

 

[dbahooker]

I agree; it would be nice.

it is a plausible idea to develop on 2000- and then when you're all
done and ready to go; run it on SQL 2005.

Running on SQL 2005 works great for the most part; but shit like
extended properties give troubles; which is a bigger problem than it
sounds like.. things like view widths, hidden columns aren't persisted
I dont think


altogether, ADP 2003 works BETTER against SQL 2005 than you would
expect.
I just would really reccomend developing it in 2000 and then restoring
it to a 2005 server

This gets to be sticky once you have real data in the database

-Aaron

 

[Mike]

hhhh

I agree; it would be nice.

it is a plausible idea to develop on 2000- and then when you're all
done and ready to go; run it on SQL 2005.

Running on SQL 2005 works great for the most part; but shit like
extended properties give troubles; which is a bigger problem than it
sounds like.. things like view widths, hidden columns aren't persisted
I dont think


altogether, ADP 2003 works BETTER against SQL 2005 than you would
expect.
I just would really reccomend developing it in 2000 and then restoring
it to a 2005 server

This gets to be sticky once you have real data in the database

-Aaron

 

[dbahooker]

yeah the MDB kids around here have never had to deal with more than a
dozen users lol

if only Microsoft rewarded the REAL access developers that could build
scalable systems-- instead of these MDB script kids; then maybe this
newsgroup would have some decent coders

as it is; it's chock full of MDB wimps; even here- - at a newsgroup
dedicated to ADP.

it makes me sick.

Yes; SQL Server and ADP can meet the needs of your system.
Get a dualie Xeon 5160 or something and a couple of sql server
developers.

you dont need DBA you need developers... in the Oracle world; a DBA is
considered a Senior Oracle Developer.. In the SQL world; this is not
the case; the DBA are the newbie kids.

-Aaron