Access 2002 jobs?????

[Robert]

Hello,
I was just wondering if anyone knows of resources to
find jobs for Access developers. When I look at
Monster.com, Dice.com, etc., it's 'SQL Server this'
and 'Oracle that' and 'DB2 the other'. With the huge
investment Microsoft has in backing Access as a member of
the Office suite, it seems to me that somewhere in this
world, there should be a demand for Access developers
too. Am I just looking in the wrong places? Thank you if
you know of anything that can help. I keep searching for
jobs for Access VBA developers, and find nothing.

t.y.

 

[Shao]

It doesn't hurt to learn some SQL. However, if you want
to stick with just Access development try getting help
from Recruiting or Temp companies. Also try software
companies. They may have positions posted that are not
listed in major job search engines. hope this helps.

 

[Victor Delgadillo]

I would try the local newspaper too!!

--
Victor Delgadillo MS-MVP Access
Miami, Florida

Mensajes a los grupos de noticia, asi todos nos beneficiamos!

 

[Pat Garard]

G'Day Robert,
'Microsofts Huge Investment' has positioned it
both as a Front End to MS SQL Server and as a
Front to Oracle and many other non-MS and
non-Windows RDBMSs.

You should consider learning SQL - a number of
applications, especially those tracking assets over
time, require a lot of SQL.

Have you thought of running your own Small Business?
We get a lot of work at the SOHO and Small Business
end of the scale.

When you seek employment, you are probably looking
at Agencies that Consult/Develop at the Middle to
High end of the Spectrum.

Access Only Low End
Access<-->Excel/Word/ASP/VBA/vbScript etc
(You are about here)
Access/VB6 (Prototype in Access, Convert FE to VB6)

Access + SQL Server
SQL Server<-->Excel/Word/ASP/VBA/vbScript etc
Access/VB6 + SQL Server

Access + Oracle .... etc etc


High End
--
Regards,
Pat Garard
Australia

Anne & Pat Garard.
apgarardATbigpondDOTnetDOTau
_______________________________________________

 

[Kevin3NF]

Robert,

As a consultant and recruiter, I have found that it is very difficult to
find a pure Access position these days, other than short-term or part-time
contracts. There does appear to be increasing demand for Access Data
Projects, and limited supply of those that can create them efficiently.
Also there is a bit of a market for getting an Access db on the web.

The best thing you can do (IMHO) is get very familiar with SQL Server and/or
a web technology such as ASP.Net.

I base this on the contract requirements that come across my desk and what
my clients tell me they want.

Hope that helped, feel free to post back with more questions.

 

[Eric Cardenas]

| Hello,
| I was just wondering if anyone knows of resources to
| find jobs for Access developers. When I look at
| Monster.com, Dice.com, etc., it's 'SQL Server this'
| and 'Oracle that' and 'DB2 the other'. With the huge
| investment Microsoft has in backing Access as a member of
| the Office suite, it seems to me that somewhere in this
| world, there should be a demand for Access developers
| too. Am I just looking in the wrong places? Thank you if
| you know of anything that can help. I keep searching for
| jobs for Access VBA developers, and find nothing.
-----------
Hi Robert,

Your question is really not a technical question about MS Access, but let
me share my two centavos anyway:

I started with computer databases in the mid-eighties of the last century.
Back then dBase III was just released superceding dBase II. Hard disks were
relatively new then and many people used two floppy drives to do their
work. Later, dBase "compilers" came into the picture with Nantucket's
Clipper. And then Fox Software took over the market share of this xBase
market.

I joined Microsoft 11 years ago bringing with me my Foxpro skills. A month
after I joined Access 1.0 shipped and sold like pancakes. Many flavours of
Access later, I have moved to SQL Server support. I still do Access support
but I get lesser and lesser calls on the product because more people are
moving to client-server technology. The last Foxpro call I did was probably
over 4 years ago.

My point is, we who do technology for a living have to be in step with the
market. It is not Microsoft who dictates what technology will be popular in
the future, it is the people who use the technology that will.

Where would I be if I stuck to my dBase III skills and lost step with the
current flavours of technology? I'd probably be serving doughnuts at Krispy
Kreme or something similar.

If I were you, I'd get out of my comfort zone and start learning about
client-server, C#, web applications, XML and all the other popular
technologies today. Access has had its glory days. You can still work with
database technologies, but the tools will constantly change.

Hope this helps,

 

[Dirk Goldgar]

I joined Microsoft 11 years ago bringing with me my Foxpro skills. A
month after I joined Access 1.0 shipped and sold like pancakes. Many
flavours of Access later, I have moved to SQL Server support. I still
do Access support but I get lesser and lesser calls on the product
because more people are moving to client-server technology. The last
Foxpro call I did was probably over 4 years ago.

I think that you're drawing false conclusions here. I've been doing
Access development for years and have never needed Microsoft technical
support. I had worked with SQL Server for only days when I was forced
to open the first support incident I've ever used in my entire life (it
was a bug in SQL-S 2000). Maybe the years of development and refinement
that MS has put into Access, combined with its positioning as an
end-user database, have resulted in a user- and developer-friendly
product that just plain works?

In all fairness, though, I can't claim that Access users don't ask lots
of support questions -- just look at the level of activity in the Access
newsgroups. But those questions are asked and answered in the
newsgroups, so the solutions come from peer support. I've seen very few
questions that would warrant a call to MS Product Support.

My point is, we who do technology for a living have to be in step
with the market. It is not Microsoft who dictates what technology
will be popular in the future, it is the people who use the
technology that will.

So you're saying that Microsoft doesn't have a vision for the future of
technological development in the software field? Hmm, I think Bill
Gates may have a different view. No, of course MS doesn't dictate the
popularity of technology, but it certainly has an impact, and
unquestionably attemps to use it.

If I were you, I'd get out of my comfort zone and start learning about
client-server, C#, web applications, XML and all the other popular
technologies today.

These are certainly important technologies, and certainly a developer
should attempt to keep up to date. But I'd expect at least some of them
to be incorporated into future versions of Access, rather than
discarding Access as "old technology". Client-server, of course, has
already been brought to Access, in the form of ADPs. It still remains
to be seen what Microsoft is going to do with Access in future versions,
but it's too powerful and too popular to throw away.

And the power of these new technologies is in allowing us to use our
computers in new ways, not in eliminating all the old ways. In my
experience, the vast majority of applications do not need to be
client-server, web-enabled, or "dot-net-ified". Let's not confuse the
vision with reality.

Access has had its glory days.

Not yet, I don't think. But if that time comes, it will be as a result
of Microsoft giving the people what it thinks they should want, rather
than what they actually need.

You can still work
with database technologies, but the tools will constantly change.

You'll get no argument from me there. Let's hope that Access continues
to change and develop, at least until something with equivalent power
and ease of use comes along. As yet, nothing has.