Microsoft Access

[Aimster]

I said I know Microsoft Access.

Guy hands me some big Access database and asks me to edit the Visual Basics code. I said I do not know visual basic and he said I do not know Access then.

What they did was build a program in visual basics to retrieve data from the database and in Access the visual basics editor popped up.
I had no idea what to do with the code for the software.

So in order to be good in Microsoft Access you need to know visual basics?

 

[bruceb]

Try this:

http://www.freedownloadscenter..._Visual_Basic_5_0.html

 

[Aimster]

but if u write know access on your resume would one expect you to also know visual basics?

 

[ChAoTiCpInOy]

How would they make that jump? Access is a database program, you don't need to know Visual Basic to use a database.

 

[KB]

Anybody can make a bowling scores/birthdays database in MS Access without using Visual Basic (please don't call it Visual Basics, you only underline your lack of knowledge about it -
this post is not meant to offend only inform); however, when it comes to doing good/user-friendly databases in Access, you eventually need to get down and use code. Its like using Microsoft Frontpage as your HTML editor. You hopefully know HTML and javascript because Frontpage can't do everything and you eventually need to do something it can't do in the GUI.

That being said, whether you should have known Visual Basic depends on the job description. If it said Database Developer needed for Access database then yes, you need VB knowledge. If it said Database Administrator needed to update and query database, then VB knowledge would not have been implied.

 

[OdiN]

Originally posted by: ChAoTiCpInOy
How would they make that jump? Access is a database program, you don't need to know Visual Basic to use a database.

In business, yes.

Access is fine for simple things without VBA.

For most other uses, you really should know VBA.

In my perspective (as a DB Analyst who uses Access a lot), yes you do not know Access if you do not know VBA for it.

Proper Access databases are of a split design (frontend/backend) and usually rely on VBA code to do some more complex things. Especially with data entry forms where there is the possibility of user error - you code things behind the scenes so that if someone enters something incorrectly, it won't allow you to. For example, a DB that I took over I made some changes to the main form because users were marking accounts as completed when the credit applications were rejected - which is impossible. The account should be marked as cancelled. So I added code to prevent the account from going into completed status unless the app was approved. Just a reminder so that they remember to put it into cancelled status.

Also - many will make the whole front end of a DB with VB. Though a lot of times I use an MDE file with VBA in it to handle the front end needs.

Access for business is much more application development than you would think.