Access 2010 SP1 – You receive random crashes in certain database or when opening the VBA window in those databases after installing Office 2010 SP1

I will admit that I think Access is and has been a very powerful tool.  But technology changes and I never accepted those changes I would still be coding in raw VB using floppy drives.  As much as I love Access I know I need to move on.

The future is moving to mobile applications (smart phones and tablets) and the coding to support these platforms has changes.  I, myself, am focusing on ASP.net, still with a VB focus on the back end.  Businesses I work with dont' have the expertise to support Access nor do they want it.  Only those who are still willing to invest give me very lucratvie projects.  But I'm trying to educate them on the power of tablets and the cloud.  Maintenance is a dream.  I fix it last night and they use the changes in the morning.  No more deplying updates with uneducated users.

The only thing that I really use Access for now is the process automation for Office applications.  Taking a week's worth of manual work getting data in spreadhseets, cutting and pasting in to Word and Powerpoint documents can literally be changed to one minute with the click of a button.  But the advances with new Office file formats now allow me to do that also in the cloud.

I aplaud Micorosoft for enhancing the techology and moving on to stay ahead of the curve.  If they are doing it, I know I need to.  So, yes, it's bad that we have this problem with Access but I can also understand why it is a low priority for them right now and in the future.

Let's just say I'm not having these problems with my ASP apps.

Thanks for your sincere optimism Paulg. I would agree that Access 97 was a benchmark for stability. The problem is that these events you are referring to occurred 15 years ago during the infant stages of the desktop database solution. SQL Server wasn't even born, much less Sharepoint, etc. The www was just getting started. The playing field has changed and as such, the focus of MS has had to adapt and lead where it’s researchers see in its best interest.

Of course there are more alternatives to Word/Excel than Access. That is probably in part because Access does a great job, but also because the there is a much larger market for word processing and spreadsheets. Furthermore, the "bug" that we are referring to affects even yet a smaller group of this small group – the developers.

These two things (Access having hardly any competing product and a smaller market), combined with hot trends (mobile, connected apps, etc.) and the rising of Google, Apple, etc. that MS has to battle, just have "put Access on the back burner" written all over it for Balmer or whomever is at the helm.

Anyway, I can just hope for a patch soon. :)

-Mike

Hi everyone

Before we go running off to find the light switch .(last one to leave - turn off the lights) .  take a breather . .

I have used MSA since version 1 . . and have watched it grow.

Sadly it seams MSA has been the Cinderella program . . always over shadowed by the ugly sisters . . Word/Excell and the cousins  . . powerpoint . .etc

I recall in 1995 - going to the launch of MS-Office95 . . i think around july - in Sydney. It was the only time I got excited about a new program version coming out . .We all eagerly listened to the fabulous new features we could expect . . hhmmmm . . only worthwhile real improvement . . you could convert a text box to a combo box . . wow !!!

But the the Big surprise  . .hooray !!!  . . MSO was shipping without MSA because it wasnt finished.

We would get an upgrade coupon  . . for Xmas. And when it did arrive it was rubbish.

So 1996 was a bad year . . all the sort of stuff that is happening now happened with MSA95 . .

Finally MSA97 was released and we could upgrade with conifdence. My enterpise system is still running  - smoothly on MSA97.

Sadly MS dropped the baby in 1999 rushing to solve the terror of Y2K . . and created another crock . .  MSA2000 . . but bounced back with MSA XP and MSA2003.

So if we consider the cycle . .  a good version is just around the corner . .(Nathan where are you?)

As for "other products" there are many alternartes to word / excell even powerpoint and outlook . . but is there really anything that stacks up to Access as a user-friendly RDBMS . .

It should be the flagship product - centralising datas management with the other programs supporting it. . . Why does Outlook not use Jet as the backend? Such a natural choice - so MSA can be be the data management system with Outlook as its email agent

• in a unified structure . . not loose linking . .

anyway enough ranting . . i am optimistic . .  they will fix it . . wont they . .

cheers

Paulg

Went to work tonight on a project that was working fine Friday and now it has problems. Cannot delete or rename any control on any form (they all have event procedures), and I cannot delete or rename any form as well.  I am several weeks into a very large project and this is starting to really scare me.  Really (really!) hope you guys fix this soon.  I recent installed SP!, and then uninstalled it cause of too many problems.  So apparently this "version" is not stable either.

I do have a work around that I do not think anyone has mentioned - most folks probably don't have this as an option at all.  Stumbled on it in desperation.

 We have a Win 2008 server with Office on it, and that version has not been upgraded to SP1.  Also - and this is interesting - it is the 64 bit version. I am running the 32 bit version on my development machine.  I can copy the "broken" accdb up to the server and everything works.  I compact/repair it there, and then copy it back to my machine, and all the problems are cleared up. 

My work around has saved my butt twice since I discovered it.  Just passing on my concerns and my observations.