Re: Visual Studio 2005 - VB or C#, etc - SOME ONE PLEASE EXPLAIN..

You are posting this question to a newsgroup where the topic is Visual
Basic 6.0. This is not the same as VB .Net 2005.

A news group that you might try is microsoft.public.dotnet.general.



Anns via VBMonster.com wrote:
This is a silly question, but I must ask to better understand.

I do development work in Ms Access using VBA and new to SQL Server and now
learning what Visual Studio 2005 has to offer.

In my mind Ms Access does so many little steps in the background for you (via
- Wizards or drap/drop) so when you think about building a database in Ms
Access its not overwhelming b/c if you compare building tables, forms, etc
with Visual Studio - everything in VS 2005 for the most part takes ten times
the steps that Ms Access tools offer.(unless you are an advance programmer)?
To build a simple form with buttons, combo box, etc in Ms Access you just
drag and drop and it automatically knows to relate that combo box to the
specific form you are working on. The wizards in Ms Access will direct the
data and do the rest for you.

Say if you want to build a web site in VS 2005, to me unless you know this
programming very well and all the steps, it's just faster to build a website
using Ms Publisher, Frontpage,etc. using drag and drop and other friendly
tools.

Keep in mind that I am new to the .net environment and I play in the visual
studio 2005 software to see all the different features and I go on-line and
watch the visual tours that MS offers about it.

My company wants to take 25 of our Ms Access (native jet databases) and put
the BE on SQL and FE's to be recreated in Visual Studio 2005 and then put the
new FE on Sharepoint (intranet).

So with all that in mind, I am trying to make good sense of this.

My question is:

*******With software already available to create db's with out having to be
advanced in code (C#, VB, VBA - Ms Access), why on earth would a person or
company want to build this stuff from scratch in Visual Studio where it seems
to be that every step is extra vs just build in Ms Access and pull over???????
????????????????
Explain:

********Why would someone want to create a website in Visual Studio 2005 with
the added extra steps (unless a programmer) when you can just drag and drop
with Ms Publisher, FrontPage?
Explain:

********When making the conversion like as mentioned above like my company is
doing, why can't the current 25 ms access databases be pulled into SQL (BE)
and the FE's still be used and view on SHAREPOINT AS IS? Why is it that all
new FE's must be built using VS 2005, instead of just keeping the old. Isn't
there a feature/property that will allow this to happen instead of having to
rebuild all those userfaces?
Explain:


Keep in mind that I don't know the anwsers to these questions and that's why
I am here.
My whole reason for asking this question is b/c why re-invent the wheel when
it's already here.

********Why build a db or web site in VS 2005 when you can do it in a program
that can do the same but easier, less programming, less steps and wizards
that knock 10 steps to 1. The same goes for building web sites?
Does it come down to Publisher the Db or Web site and that why programs like
VS 2005 have to be used?
Explain:

*******Should we all thank the software developer/engineers that created
these wonderful programs that elimate all those steps?
Explain:

--
Message posted via VBMonster.com
http://www.vbmonster.com/Uwe/Forums.aspx/vbasic/200607/1

.