The reason I asked is that my Access teacher told me that if one is very skillful in using the Access Interface itself e.g. queries, expression builder, macros, many times one doesn't need to use VBA or even doesn't use VBA in the whole project.
I agree with this statement. You can build accomplished solutions without using VBA (to a point). It's actually quite impressive how much automation macros can add to a solution. However, I agree with everyone else, that you should focus on VBA.
For simpler solutions, you can get some nice functions pretty quickly using macros with little effort. But as the function complexity increases, macros become harder, if not impossible to write. VBA may be a bit tough to get started with but it quickly overtakes macros as complexity increases. Inevitably you will find yourself having to step into VBA in any case.
As an example, a common task is to send an email with multiple attachments. I think if you are using a macro then you are stuck with the sendobject function so you can attach multiple attachments. On a similar vein I guess that you can't do any object manipulation in macros? e.g. playing around with an excel spreadsheet. I read
here that you can't use DAO in macros and that's a biggie imho.
One other reason for considering learning VBA is that for the most part it is a transferable skill. Many of the concepts in VBA are core to many other programming languages (loops, if statements, subs, functions, datatypes etc).