boblarson
Smeghead
- Local time
- Today, 01:43
- Joined
- Jan 12, 2001
- Messages
- 32,059
Then you would need to take 1997 off the list too.Not if you extensively use images.
Simon
Then you would need to take 1997 off the list too.Not if you extensively use images.
Simon
It was SP3 that actually caused the problem. They had to create a hotfix for it (they eventually fixed the SP I believe). But that had to do with some security stuff they had done due to Windows XP. So, outside of that issue, it has been quite stable and works well. Much better than Office XP.Didn't Access 2003 have a hasty bug that was not resolved until SP3?
I have to agree with all the above. I've taken a look at the information on the "What's New fo Access 2013" page and don't like what I see at all. I'd hardly describe myself as some luddite clinging to old technology, but I've got a sprawling ADP which has developed over the last 6½ years and can't afford to chuck all that away to change it some feature-limited web app.
I've been putting off upgrading to 2007 or 2010 due to the hassle of coding the ribbon (even though I can see it offers some nice interface possibilities) and thought I'd skip straight to the new version later this year; now I guess I'll have to concentrate on 2010. In my experience, "everyday" users don't bother with Access and just Excel instead (infact most of them don't even know what Access is for), so I can't understand why MS seems to be tailoring the software around them. Why not instead concentrate on putting some new features that developers might actually use?
I'd love to see some easy to implement, hardware-accelerated eye candy effects, such as animations or transparency. It seems extraneous but used in a tasteful manner I think these can really improve the user experience and it's what users are coming to expect nowadays. Or even better (and it's been said many times) having an easily programmable ribbon!
.
You should purchase 2010 now before the new version comes out. At least that one is not going to look like crap and have a lot more things you'll need to edit your database for. Yeah, you'll have some things to modify due to the Ribbon, but it won't be as much to update if you wait and go to Office 15.I will have no choice but to purchase whatever the oldest version with the most patches will be available then but I am not looking forward to it.
SHADOW
It does seem that only every ten years does Microsoft put out a really good, substantially improved and developer friendly version of Access:
1997
2007
There are only four years to wait!!!
Simon
You should purchase 2010 now before the new version comes out. At least that one is not going to look like crap and have a lot more things you'll need to edit your database for. Yeah, you'll have some things to modify due to the Ribbon, but it won't be as much to update if you wait and go to Office 15.
You're probably right. I'm taking a gamble if 2010 will still be available for purchase in two years (it's possible, I suppose). I just find it hard to spend money on a product with so many known bugs and only one service pack that screwed things up so bad that Microsoft's "solution" was to create ANOTHER update to remove the service pack. And hitherto, no solution to the problems.
I suppose I can buy it now and let the disk collect dust for 2 years...
SHADOW
If you wait, you will only be able to get a copy off of eBay and that can be dangerous as you don't know if it is a legitimate copy or not. When the new version comes out, the old version typically may be around from some retailers for a short while but most of them are returned to Microsoft due to their marketing agreements (I do believe). So getting a copy might be hard to get. I'm just sayin...
ProbablyHi
Another shame and I can not understand is the exposure of the password back-end, the MSysObjects table. This ridiculous failure, will be eternal?
Not really. VBA will be around for quite a while still as it would take a lot to replace it. The macros are being expanded because macros are the only thing that can be used in a WEB database. You can't use VBA in those so the functionality has to be there. The team has said that VBA will still be around.The VBA has not been changed by your END is near. Gradually be replaced by MACRO, which is being remodeled and enlarged.
That is not quite true. Little bits (bugs) can change, but additions and subtractions are finished. If they weren't done in the Technical Preview stage, they won't be done now until at least the next version. The Public Preview is just an expanded bug finding mission before RTM (release to manufacturing).Since this is a Preview, a lot can change. I hope so!
Does anyone know what "the Power IW" is? I did some web searches with no success.
SHADOW