Interaction with VB/VBA

Hi there,

I've just started learning SQL - I already know a bit of VB/VBA and my aim is to become a software developer using both SQL and VB.

One question I have is how would the average programmer go about managing the database? Are SQL commands (queries/add record/make table etc) normally programmed and controlled in VB itself via the docommand.runSQL on the event triggers or are they managed from the SQL Server application themselves? Also, if there are any other comments on how VB works with SQL I'd be very interested to hear them.

My assumption is that the database commands are managed from VB and any automated download/import or export of data into or from the SQL database is scheduled from SQL server itself.

Many thanks for your time in reading.If you use MS SQL Server 7 or 2000 you can use Enterprise Manager to manage your databases. If you use SQL Server 2005 then you can use SQL Server Management Studio to do the same.

You can connect to your SQL Server db from VB6 with ADO and with ADO.NET from VB.NET.|||Many thanks for your reply - how about if you're using MS Access for the front end?|||ADO works fine when using Access as a front end. Even better if you use an adp. You can use the majority of your VBA functions from access if you like. However, a wise developer ports the lionshare of their data-centric business logic to the database itself.|||Many thanks for your reply - how about if you're using MS Access for the front end?

If you use MS Access the only difference will be that you'll manage your data from the MS Access environment, but you will still use ADO and ADO.NET from your VB applications.|||If you are using SQL 2K and you are wise you will avoid Enterprise Manager and use Query Analyser. EM is a GUI, QA allows programmatic access to the database - much more powerful and much more flexible.

DBAs don't typically use Access or EM to manage a SQL Server db but YMMV depending on how much control you are looking for.

HTH|||If you are using SQL 2K and you are wise you will avoid Enterprise Manager and use Query Analyser. EM is a GUI, QA allows programmatic access to the database - much more powerful and much more flexible.

DBAs don't typically use Access or EM to manage a SQL Server db but YMMV depending on how much control you are looking for.

HTH

I use EM daily to run hand-built queries and I do have programmatic access to my databases. I use QA too, but for the most things EM is just fine.|||yeah but if you script everything, you are more efficient because all you have to do is it hit f5 and you have less hassles when sql goes to a new version and your ui changes.