[AccessD] ADPs in the future

> So now's perhaps the time for alternatives ...
>/gustav

Hear, Hear.

This is yet more evidence that Access is dead. Despite its unique
advantages, Access is increasingly obsolescent in the current Microsoft
vision of .NET, SQL Server, web-centric, and distributed computing.

More evidence of this comes from recent reports of a precipitous drop in
Access consulting rates in our local area. How low? Let's just say you could
earn more if you were a certified welder than if you solely designed Access
databases. Around here, large businesses are simply not doing serious Access
development. There are still small to mid-size businesses that rely on
Access, and they will provide the bulk of Access-related jobs in the coming
years, but even they will dwindle over time as newer tools gain market
saturation.

So, fellow AccessD posters, I would gently suggest that we all take a
serious look now at alternatives that will provide a better source of income
in the future. We must start developing competence in new areas, because
opportunities in Access will likely dry up in the next couple of years.

Its no fun seeing the skill set that you have worked on for so many years be
thrown away so casually, but that is simply a harsh fact of life when you
depend for your livelihood on a company whose market imperitives demand
obsoleting the current code base in order to sell the next.

-Ken

>> There is no service pack or quick fix being planned as far
>> as I know because of the amount of work it would entail.
>> If you stop to think about it, it's pretty hard to see how
>> accomodating new Yukon features like CLR assemblies and
>> complex data types in the ADP designers could be achieved
>> without a complete rewrite.
>> --Mary Chipman