Re: ADP or C#/VB.NET


Access dose Rock when it comes to getting it done fast. But, it rocks
old school and all the cool kids are listening to .Net. They think
rock sucks. But, cool doesn?t pay the bills; and as long as MS is
around Rock will never die.

I would suggest prototyping in Access and leveraging the sequel server
for managing as much business logic as possible. The powerhouse of the
multi-user environment is really the database. Every application has
different requirements in respect to data; however a properly deigned
SQL db should have no troubles supporting 20?30 users, if a common
sense practices are used in creating the user interface. For Instance,
designing and interface to be exclusive in retuning records instead of
inclusive.

Example: A drop down box could be empty until the user enters it.

Also, consider your design methodology. J2EE suggests that rapid
prototyping is often the most efficient way to approach application
development. Access is an excellent tool for this. It also has
definite short comings.

Example: the ADO errors collection is not exposed this makes it
somewhat difficult to catch and handle all the errors a user could
encounter and inform them of appropriate action.

However, any database development including stored procedures and user
defined functions will be available for future work, allowing for the
migration to a different enterprise architecture or user interface.


--
chakatheapemanPosted from http://www.pcreview.co.uk/ newsgroup access

.

Quantcast