chosing between Access and VB.net - coupling data to objects
Posted on 2004-09-18
I'm about to co-develop a inventory/customer/order/invoice kind of database application. The application is for intranet use in small workgroups (up to 10 users or so). I need help chosing between access and vb.net.
I like access because of the ease of building forms and reports, and there is no coding involved to get the data on master/detail forms and update the data.
If building forms was as easy in access i would chose vb.net because as a java programmer so i like OOP (for more easy to maintain and extend code). On the other hand i don't have database expierence in vb.net. I looked into vb.net/ado.net but to seems quite hard to couple data to objects and place properties from those objects on forms (i.e. a object customer that gets data from db, and exposes properties as 'name', and i put that property on a form as a textbox). I also looked at tools that generate the data/business tier (money is not the primary issue). Also i don't know if crystal reports is as easy as drag and drop 'reports' in access.
Wich one should i chose?
Is it easy to use 'business objects' on forms in access and let the datalayer be generated? Or is this overdone for this size of project (although i might want to expand in the future)? Pointers to tutorials/samples/architectual examples are welcome too as long as they make it clear for me if vb.net is a good option to chose, and NOT more work in the long run.