SQL/Visual Basic...

[jenni]

My boss is willing to send me to a trainings seminar, so that I can enhance my capabilities in Access.&nbsp;&nbsp;I posted a question titled &quot;Top Select&quot; and cornerstone responded with an expression....dim getsql as string....etc.&nbsp;&nbsp;Is this SQL?&nbsp;&nbsp;Can you use SQL for modules?? When and why should I use modules? What is better for me to learn?&nbsp;&nbsp;SQL or Visual Basic??&nbsp;&nbsp;I had heard from a colleague that in modules you cannot use SQL.&nbsp;&nbsp;Is this true?<br><br>I would love to understand the answers and tips that the teks post.&nbsp;&nbsp;Can anyone recommend what I need?<br><br>Thanks.

 

[famousb]

personally, i would learn VB first.&nbsp;&nbsp;it can incorporate SQL into it's expressions, and it allows you greater flexibility with your Access programming.&nbsp;&nbsp;i'd say 99% of the tips posted here are in VB, so if you want to understand them more, go that route.<br>SQL (Structured Query Language) on the other hand is good to know to be able to write queries in a non-Access environment, and would be good if you ever plan on doing anything with say, Oracle.<br><br>I, myslef, am a self-taught VB person, and picked up alot of it from just trying to figure out other people's code and what it means (for all you true VB gurus out there, now you know why my things can be round-about sometimes).&nbsp;&nbsp;Now i am trying to learn a little more SQL, and i do that by looking at my queries in SQL view (which is through the view menu along with form and design).&nbsp;&nbsp;technically you could write all of your queries in SQL, or you could use the SQL in VB code.&nbsp;&nbsp;when i need SQL for VB code, i just create the query that i want, and then copy and paste the SQL into the VB.<br><br>so my vote is for VB, but make sure that the class you take is VB for applications, you want to be able to apply it to Access.<br><br>good luck.<br> <p>Brian Famous<br><a href=mailto:bfamous@ncdoi.net>bfamous@ncdoi.net</a><br><a href= > </a><br>