Slow learning curve or is it me?

[Reese]

Those who've seen my posts have probably noticed that I have a lot of questions and need a lot of help.

I feel really bad that I keep coming here with so many issues. I have a rather big project that I'm working on and I'm learning as I go.

Still, I feel like I'm either cursed with technical issues, an idiot, or have simply taken on far more than I can chew. Am I alone in this situation or is this pretty much the standard learning curve?

And to all of those who have helped me on this form, a big thank you. I hope I haven't been too annoying.

 

[penfold1992]

Still, I feel like I'm either cursed with technical issues, an idiot, or have simply taken on far more than I can chew. QUOTE]

Probably a bit of all three there mate!

Nah, the issues would be much fewer as you understand what it is that Access is able to do.
Access is a very in depth program which can do a lot more than you need it to do and its trying to find the right parts/sections/coding to achieve exactly what you want and that is a very personal and specific thing.

taking on too much is quite a common issue for programmers which is why a lot of them ARE programmers, they strive for that challenge where a big reward lies at the other end, the journey is the discovery of the techniques and the learning which lots of us crave.

there are certainly many aspects that I dont know about Access and the guys here can always come up with a solution or a work around and just reading some of the posts can give you good ideas so definately keep at it.

is there a specific area you find more difficult than others?

(oh and i ask lots of questions too so, we can be hated together )

 

[spikepl]

Coding is like a foreign language: it takes time to achieve fluency, but then so many others have done so so why not you too.

Also, each new langugae is easier to tackle, because of the exeprience with the previous ones.

Finally, letting oneself get frustrated by errors and mistakes is just irrelevant, immaterial and counterproductive. Like Edison, who when asked how could he continue after having failed 10,000 times in finding a suitable material for the light bulb filament answered: I haven't failed. I have discovered 10,000 ways of how not to do it.

 

[Reese]

Thanks for the pep talk guys! While I do get frustrated with some of the individual issues that come up, I'm more sheepish about my ignorance vs. frustrated--at least when looking at things as a whole.

By the way, spikepl, while Edison has many great quotes which are inspirational and wonderful, he really was a dick. See what I mean: http://theoatmeal.com/comics/tesla. It doesn't take away from the truth of the failure quote, it just means that he wasn't all that and a bag of chips.

Plus, I love spreading the awesomeness which is Tesla.

 

[penfold1992]

get frustrated and angry if you want.... as long as it doesnt make you quit wanting to learn....

ill sometimes get very angry with myself for not knowing how to do something but the guys at work hate it when i shout "YES!!!" when I finally get the correct answer

 

[Sanci]

You are not alone.
I get upset and angry(sometimes even growl at monitor, not something I'm proud of), and than cool off (take power nap), and start over.

It helps if I speak to somebody, you may be suprised how different perspective can be useful. But when I'm alone, here is one quote that helps me:

"Happy is the man who has broken the chains which hurt the mind, and has given up worrying, once and for all."
"Be patient and tough, one day this pain will be useful to you."

 

[gemma-the-husky]

reese

no, it's not you. access (databases in general) is a very complex affair. it is so complex that a lot of stuff in a database is designed to prevent users using the full power of access.

it's akin to developing a complex spreadsheet, and then locking down pretty well all of the cells, and only permitting input into a small range of cells - which may well be the approach taken in big organisations who design stuff like financial modelling spreadsheets.

for a complex practical database, you need to understand data analysis to derive the correct table structure. you need to be able to develop forms and queries to use the tables. you need to be a pretty good to expert coder.

the concern in your post is that you are talking about a "big" project. if you are not already comptetent, i am pretty sure you will make little real progress without help.

try a small project first - eg something apparently trivial like a CD database and you will see how difficult it all is.

the idea of a "database" sounds enticinbg. in practice, you are trying to build a professional turnkey application of the type you might pick up in a computer store. That's how good it needs to be.

eg - how much would you expect to pay for a pre-packaged application of the type you are looking to buy (if there is such a thing). it will almost certainly "cost" you at least that in your own time to develop the same thing. the benefit is that you can leave out stuff you don't need, you don't need to make compromises in particular areas, and it hopefully won't cost a fortune in ongoing maintenance and support.

 

[Lightwave]

I think there are two main benefits from learning Access Databases.

• Understanding of data structuring - ie relationships
• Understanding of the subtleties of good UI design

These two aspects are the same whatever stack you are in and even if you don't attain the level you wish to - any experience will make you much better at choosing off the shelf products. I'm fairly confident now that while I may not be able to design everything myself I can spot when a salesman is trying to sell me a Turkey and I think I have a good framework within which I can choose to go forward with systems.