Last post Jul 22, 2007 07:50 PM by DavidKiff
Jul 22, 2007 05:15 PM|Henrybsmith|LINK
Help! I am confused and am having difficulty seeing the objects and relationships of the components of an interactive DB web site and how it all goes together. All the books I have read take me from exceptionally basic examples to down in the weeds with
no big picture relationship view. I feel like I have to go back to something near assembly language programming to achieve a web site. Please tell me this is not so.
My machine has XP Pro, MS Visual Studio 2005 Pro, MS Office 2003 Pro, IIS installed.
I have a Access DB application for a Property Owners Association (split DB) that I am trying to migrate to the web to achieve a single data source for the 5 board members. At the moment I have to provide each board member with an update data each 3 months.
Application has many tables, queries, many forms and modules for integrity control. I have read several books, but am still confused as to where all these elements go and how to interact with them to perform CRUD and reporting. I am expert with VB. VBA.
SQL and Access DB programming.
Can some one provide me with a Pareto (block diagram) of how all these pieces go together and relate to form a web interactive program to achieve a Access DB CRUD? And of course allow the selected members to obtain predefined reports related to the DB content.
I appreciate your time and attention to this matter and look forward to your response.
Henry B. Smith
Jul 22, 2007 07:47 PM|DavidKiff|LINK
Hmm an expert in VB and SQL but unable to see the relationships!?? An expert in SQL qould certainly avoid Access!!! Have you tried SQL server? This has obvious scalability prospects and is designed for multiple users. I find acess good for a teaching
Any way. Three tier archicture seems to be the way forward. This is three seperate logical components, GUI, Business Logic and Data Access.
Your data access classes obtain the data and return it to your business logic. Here the logic is perfomed on the data and then passed to the presentation (GUI) tier.
You store all your queires as stored procedures (if your really stuck on access use inline SQL).
I hope this answers your question
Jul 22, 2007 07:50 PM|DavidKiff|LINK
It might be a good idea to start here :