Error Trapping on Functions & Procedures

[patentinv]

Hello,
I'm currently working on re-writing my db from Access 97 to Access 2003. I will be making a runtime version of my db. Using the Visual Studio 2003 Tools for the Microsoft Office System, which has the Access developer extensions on them.

I was told I will need to have decent error trapping for all functions and subs for a runtime db, I'm not sure what this means, or how to accomplish this. I don't believe I have any functions or subs, in my db. How do I know? I believe I only have tables, forms, report and macros. Does this only relate to vb code?

Thanks--Any suggestions would be much appreciated.

 

[Newman]

It is related to VBA code. The thing is that we use to make procedures and functions instead of macros. In a professional way, macros aren't much used, nor are the wizards for command buttons, combo-boxes and such. VBA gives you the opportunity to bring your macro to a higher level, while making them more customizable and giving you the possibility to handle errors easily.
If you know anything about VBA, I suggest that you start using it. Else, if you have the time for it, take a good book about VBA for Access. You'll see that you can do much more using VBA than macros.
There is plenty of good suggestion book on other thread in this forum. Just make a search with «VBA book».

 

[WayneRyan]

PatentInv,

You can also use:

Tools --> Macros --> Convert to Visual Basic

The macro will be converted to VBA and you'll find it on the Modules tab
of your database window. Not the greatest code, but it will get you
started.

Wayne