Spyder1000
Technical User
I enjoy working in Access but what's the future of the product? I've noticed new MS 2005 products coming out but no 2005 Access. Will there be a future release? or will it be replaced by something else?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What's the future of Access?
- Thread starter Spyder1000
- Start date
- Status
I'm a Microsoft Access MVP I have seen on-line demos of some rather cool new features coming up in future versions of MS products. I can't divulge details but I can assure that Access is not going away.
Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]
Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]
It seems to me that a better indicator of the future of Access would be the Help Wanted listings. When I enter "MS Access", a very large number of hits are companies looking to migrate to something else. If there's no market, eventually Microsoft will drop it.
MichaelRed
Programmer
The topic is at least confusing. Ms. has publically announced the demise of VB, while not mentioning that the Office suite uses VB(albeit "(A)" as the language suppporting the "MACRO" function of the suite.
ye venerable VB is being 'enhanced' to VB.Net, with little indication of how the office suite (along with the several many third party applications which also use it) will move from using VB to VB.Net.
It would APPEAR that what /whom ever is using VB will need to use VB.NET at SOME point, but then VB.NET includes some of what is currently in VB, so the murkiness just gets murkiwe. When does VB (as in VB(A) actually disappear? How much of Core VB & the applications extensions will simply transmorgify into the same functions and capabilities, and how much will actuall change?
To put this in perspective, think back (for those old enough) to the demise of DOS. How much of it remains in the costume of "Cmd"? Last time I chacked, it seemed like the traditional 99.9%. Will this be the "fate" of VB? How can it NOT be? To me, even the 999# gorillia is not likely to be interested "monkeying" with the aparent cash cow prize winner.
MichaelRed
ye venerable VB is being 'enhanced' to VB.Net, with little indication of how the office suite (along with the several many third party applications which also use it) will move from using VB to VB.Net.
It would APPEAR that what /whom ever is using VB will need to use VB.NET at SOME point, but then VB.NET includes some of what is currently in VB, so the murkiness just gets murkiwe. When does VB (as in VB(A) actually disappear? How much of Core VB & the applications extensions will simply transmorgify into the same functions and capabilities, and how much will actuall change?
To put this in perspective, think back (for those old enough) to the demise of DOS. How much of it remains in the costume of "Cmd"? Last time I chacked, it seemed like the traditional 99.9%. Will this be the "fate" of VB? How can it NOT be? To me, even the 999# gorillia is not likely to be interested "monkeying" with the aparent cash cow prize winner.
MichaelRed
- Status
Similar threads
- Locked
- Question
- Locked
- Question