Advice - 'The Next Step'

[AUGuy]

Hey Guys,
Looking for a bit of advice from some of you old hands. I've been working with access for about a year now and have come to a great working knowledge including programming functions with VBA, integrating advanced techniques into my database far beyond what I ever though i'd be capable of when I was first tasked with learning access in my job duties. I work in the financial sector and am able to study out new ideas for DB design and new modules to bring into use and it has been very beneficial to both my department and the institution I work for. I enjoy working with Databases, finding out new ways to try things, and integrating these ideas into tangible concepts to present to management.

That said, I think I want to pursue professional development with Access and obtain some 'official' training. Everythign I've done and learned to this point has been with the aid of the MS help files, this great community, and random books. Therefore I'm not sure I have a firm foundation in DB Design theory and a more advanced understanding of programming in VBA. I feel like I go to the cookbook to see what ingredients to put together to make what i want. I'd much rather have the knowledge to be able to write the cookbook, ya know?

What is a good plan to achieve this goal? Perhaps sharing some of your own tracks would be helpful. Hope this is an OK thing to post here, I figured with all the great minds who are Access die-hards that you could give some great pointers.

Thanks!
G

 

[Trevor G]

Hi G,

There will be many people in this community and else where that will have there own thoughts and styles on Database Design and Techniques. Every time you consider the needs for the database and users you tend to adapt a variation of your preferred Technique.

Some basic things I tend to consider is:

What is the overall purpose of the database
Has any other system (paperwork spreadsheet or other) been used previously
What resources can I use (software/people to ask questions as well as testing), and what can be gathered/supplied
What is the time scale (how frequently can you plan a meeting/testing session)
Create a proposal which indicates the structure and end result and time frames (if possible)
Consider your plan carefully
Work out the normalisation theory/rules
Consider the end result (structured reports/modules)
Plan the model (consider stage design (Steps to success), you need time frames)
Work within the naming convension
Consider Front End/Back end design for users/administrators/support programmers
What kind of support can you give once the database has been designed
Then go for it

These are my own basic considerations. There will be many websites and people who will give different types of advise and plans mostly based on there own experiences, which is invaluable.

If you search the web you will find a good number of Theory to design a database. Here is a link to one in particular who has over 30 years or experience and has desided to place down on paper (web pages).

http://www.databasedesign-resource.com/

I hope this may help you on your journey.

An after thought.

Learn the stages of programming from Tables/Queries/Forms/Reports in any order or combination. Then the options to programme to other applications and controlling them is very useful.

Most definately be part of a community like this, as you get stuck on something its good to bounce ideas and see other peoples work arounds/solutions which most definately will enhance your own skills.

 

[AUGuy]

Thanks, great reply! What about certifications or education? Are there any that any self respecting DB admin should pursue?

 

[Trevor G]

Microsoft will have a number of options about certification, it would be costly though you sometimes don't get enough time to work through workshops etc.

You might want to consider using the Open University so you can do it at your own pace and get a good qualification.

Look at this link.

http://www3.open.ac.uk/study/undergraduate/computing-and-ict/index.htm

I would also consider this as you would be able to see other applications and work (meet) with other people who will generate some great ideas (Probably bad ones to).

 

[gemma-the-husky]

Its always a problem. I think many/most of us are self taught.

All you often need is guidance at specific points. How do I solve this problem, sort of thing. And a few apposite techniques at particular points.

And loads of practice.

So its more of a mentor really, than specific training, I always think.

eg - take a simple thing like sorting data (not really a database problem, but as an example) . There are lots of approaches, ranging from cheap and cheerful bubble sort, to advanced quicksorts. When you investigate you see that the latter are more complex, but are more efficient for large datasets.

So there are two things - one is developing a solution/algorithm that works for your problem. The second is doing this in the most effective manner (or at least in an effective enough manner). Its an art, as much as a science, and its hard to formally train this sort of thing.