If you are familiar with Access, use it.  Dot net has a steep learning
curve.  BUT, if you are using SQL, make sure to learn how to utilize it
fully.  Use stored procedures and views.

I personally am in the process of moving to Dot net, but our main app is
still in an Access ADP and it will stay that way as it is way to big to
convert.  I am using Dot net for any new apps and/or functionality that is
web based or can run seperate from our main system.  The nice thing is that
wither way, the data is in SQL.

As far as performance, SQL can handle A LOT of Access users, IF it is
written efficiently.

Dot net is geared toward disconnected data access and takes some getting
used to.

Regards,
Jim

llA> He thinks that a performance of SQL server is seriously diminishing if
llA> there are more ACCESS Front Ends Connections to the server !?)

connections themselves are harmless; that is, if you connect and do nothing,
there's no load. Each Access project usually opens 2 connectins to sql
server.

As for the activity, production application does not do with sql server
anything unusual. There's certain extra activity during the development -
for instance, Access is gathering information about all relationships in the
whole database.

Vadim Rapp

ºÃµÄ

"ljubo l via AccessMonster.com" <forum@AccessMonster.com> дÈëÏûÏ¢ÐÂÎÅ