whereas now all they do is listen to others complain and fill there day comming up with new ideas of how to keep their own positions alive.
Well, first and foremost, my day job is working at a USA Federal government site. If you don't think I see that sort of thing going on every day, you need to think again. Trust me, I understand your comment initimately well.
"Accounting" is what you like, but the question is, what part of accounting? I'm going to wander around a bit and come back to that question.
I'm a chemist by original training, but what I did for my first "real" job was to be the "chemistry-related math formulas" guy for a small company that did automation projects of industrial products. I designed and/or wrote the Real-Time Data Acquisition software for their evolving product line, because RTDA was a secondary skill I had to pick up as a research chemist. Sort of by default, I became their operating systems expert, device-driver writer, and bits-and-bytes guy.
These days, that kind of work isn't so easily available, so I allowed myself to evolve. I'm still in the computer field, still working with operating systems, but no longer into device drivers and real-time stuff. The point I'm making is that the world evolved and my viewpoint had to evolve with it. I didn't fight that evolution.
There was a time when "putting food on the table" was a priority and I had to do what I consider drudge-level computing. So I understand the "survival" comments. After mom came down with Alzheimer's and the company I worked for got bought out and relocated, I took a job with a 25% pay cut so I could stay near her nursing home rather than blindly leave her to the care of the nurses without regard to what happened to her. And her doctor advised that moving her would not be a good idea either. So I
had to change directions in order to keep up with family obligations.
I had to live with survival priorities until she finally passed on, so I stayed where I didn't like the work, but at least the people were nice. When I was able to do so, I searched for another job, one that brought me back to operating systems, though now I shepherd them rather than do device drivers for them.
Where this is going is simple: What you like may have to evolve. After all, as you mature and go through life's other changes, your likes and dislikes will probably change. There's an old Chinese proverb that, loosely translated, says "we are a new person every five years." Meaning (I think) that a person who knew you five years ago and who met you again today would see changes in you that you didn't see because for you they were gradual.
My advice to you now is this:
I, myself like ACCOUNTING
Think about what it is about accounting that you like. Accounting is a broad, impersonal field, just like chemistry or computing. Are you a procedures guy or do you actually like to shuffle paper or do you like to do the math portion?
I am reminded of the young officer from
Bridge on the River Kwai who was a bank accounting clerk. In WW II that meant he added up columns of figures by hand. How much fun could
that have been - but he was in accounting, too. You can't do that these days because of computers having replaced that particular job, but there are other jobs you can do that keep you near accounting.
So you have to ask yourself what it is that you like about accounting. Reduce that to its essence. Don't worry that it might take a while to do that. What you want to do, though, is look to the factors in accounting that give you the pleasure you felt about that job. THAT is what you seek to do.
I'll digress again to illustrate my own search for what I liked. As a college chemist, I was a mechanisms guy. My dissertation was on the mechanism of a reaction and the process of analyzing its flow - looking at the interplay of chemicals to form the intermediates of the reaction before finally producing the final compound. That field is called "Chemical Kinetics."
As a computer device-driver guy, I was again a mechanisms person. I saw how things flowed inside the computer to take data from point A to point B. I wrote code to facilitate that data flow by controlling the data flow devices. Again, I was looking at how things worked.
As an operating-systems guy, I watch the computer scheduler processes, security arbitration processes, etc., because there I am looking at the interplay of the software components that make things work. I'm again a mechanisms guy. Lately I've had to pick up some networking expertise. Again, a matter of watching data flows and learning how the components work together.
If you tried to map that career, it would look like a bus tour with a drunk driver at the helm, steering in no particular direction. Looking back, I can see the twists and turns I've had to take to get where I am. I'm amazed I didn't go bonkers myself.
All of this works for me because it is all about learning how things work beneath the visible surface - and applying that knowledge to the practical problems around me. At bottom, I like knowing how things work together. I'm a systems analyst.
Note I didn't say "Computer Systems Analyst" - though I could. Systems analysis is all about understanding the interplay of parts that make a whole. Finding problems with the flow from point A to point B. Smoothing out or facilitating that flow. That job applies to computers, factories, the court system (not the laws, but case management), small and large businesses... everywhere of any consequence. That is what I liked.
It took me a long time to figure out that part of me. It wasn't overnight. When people asked me what I liked back on the other end of my 35+ year career, I gave them semi-accurate answers. But some time ago I learned what I really enjoyed - the mechanistic systems analysis viewpoint - and turned that into a skill set that keeps me employed.
Why the massive essay? Because I needed to show you that it ain't an overnight thing and it ain't a simple process to figure out. It took me many years to get to this understanding. Once I learned what I really liked, though, I found ways to turn that into contentment with what I do. And to turn that into my bosses' contentment with what I do. Because I can also do that (to some degree) with Access, it is again turning what I like into a useful skill that strengthens my job position.
It is what you will have to do for yourself. Don't expect overnight results. You have a whole career to steer. You will always have some level of frustration with your job, Adam. You can fix that in two ways. First, identify what you like to do at a very low level and associate some part of your job with it..., or second, find a new job where that base-level factor that you enjoy is somehow maximized.
For the amount you paid to get it, there's my advice. Hope it helps.