Access programming

[ppataki]

Dear All,

I would have a very basic question:
if I would like to leran how to create a module in Access, exactly what programming language do I have to learn?
Is it different in case of Access 2000 or 2007?

Many thanks in advance!

 

[DCrake]

A module in Access is simply a briefcase/filing cabinet where Functions and Sub routines, public variables, declarations, etc. are kept. These tend to be public and as such are available to every part of the application. The language used is VBA Visaul Basic for Applications. A language common thoughout Microsof Office. Similar to Visual Basic but with variations and limitations.

Look at some examples on this forum to see how it works.

David

 

[jal]

Dear All,

I would have a very basic question:
if I would like to leran how to create a module in Access, exactly what programming language do I have to learn?
Is it different in case of Access 2000 or 2007?

Many thanks in advance!

Modules are highly recommended but I don't usually feel any pressing need for them.

Instead I create a new form, drop a button on the form (cancel the button wizard), right-click the button > Properties > Event > On_Click > EventProcedure and click the ellipsis. If you named the button "btnProcess" you'll now see this VBA code:

private sub btnProcess_Click
'put your VBA code here because this code will run when the user clicks the button on the form.

end sub

Generally I only need a module when I am creating a UDF (user-defined-function). A UDF is super-cool thing - it allows you to literally extend the SQL language using VBA.

 

[jal]

And as far as I know, VBA is pretty much the same from Access 2000 to Access 2007.

 

[Balr14]

I'm not a great VB coder, but many of the things that worked in VBA 2000 don't work in 2007. I think most are related to changes in DAO and variable declaration.

 

[Rabbie]

I'm not a great VB coder, but many of the things that worked in VBA 2000 don't work in 2007. I think most are related to changes in DAO and variable declaration.

I think you'll find that ADO was the default in A2000 while DAO is the default in A2007. I have successfully migrated a database written originally for A97 through A2000, A2002, A2003 to A2007 without problems. The only significant change was when moving from A97 to A2000 I had to make the DAO references explicit.

 

[Balr14]

That could explain some of my current problems.