2007 SP1 is Ready!!

Can we get a list of improvements that affects access and access runtime. thanks

Not a good start for me. All seemed to install correctly. Ran A2007 OK then switched to A2002 and back again to see if the 4 minute delay while A2007 re-jigs itself had been reduced. Took about the same time and then told me it needed to reboot, but then told me I couldn't exit Access (2007) at that point. Took the offered option of forcing A2007 closed and packed up for the night.

This morning, I launched A2007 and it went through its usual 4 minute rejig and then told me it needed to reboot. I said OK, but then it told me it couldn't close Access 2007 just like last night. This time I clicked Cancel and it spent some cancelling whatever it needed to cancel. Am about to reboot to see what state my PC is in. Will keep you informed....

WOW, thanks Microsoft. My PC is now in an endless loop. Have rebooted my PC again (see previous post) then launched Access 2007. It has started its 4 minute reconfiguration routine again. That's the third time in total.

When I come back from kicking, I mean walking, the dog, I shall re-install Access 2007. Not impressed. Further notes. Got a warning about a serious error with my Adobe Acrobat PDF add-in thingy (not the Microsoft one), which I disabled when launching Access.

My Access 2007 is now unusable. Following on from my previous post, I tried reparing Office 2007. I still got the interminable reconfiguring whenever I launched a database in Access 2007. Next I uninstalled Office 2007, reinstalled it, closed all the processes I dared close, then installed SP1 again. I still got the reconfiguring whenver I tried opening a database in Access 2007. Next I uninstalled Office 2007 again and did not install SP1. I still get the reconfiguration messages. Lastly I tried cancelling the message, only to get a Windows Update message. Cancelled that too. Tried opening a database again. Some minutes later the database opened but reported errors. Tried another database and up comes the reconfiguration window again. Since this takes 5 minutes now, I shall cancel this. Brilliant. Looks like I shall have to reinstall Vista. What a farce!

Perhaps I should have twigged that something would be wrong when I saw that:

1) Originally the page Zac links to said that the SP was for a range of programs inc. Frontpage 2007! This reference has now been removed.

2) The link from that page to the list of things SP1 sorted out was not working last night (it is now).

3) Now that that link is working the Excel spreadsheet which is meant to list the things done in SP1 is currently unavailable.

4) The page that is meant to show you how to overcome the interminable rebooting contains a significant typo which shows that it has not been checked problem. On this last score, it may be me (quite likely) but the set up for logging the cause of the problem does not work on my Vista machine.

SP1 installed without problems and my application runs fine. I am also pleased with a slight reduction (maybe 5%) in the source (.mdb) and compiled code (ade version). Well Done!

I've installed SP1 on two computers without incident. Time to switch between Access 2003 and Access 2007 is about 25-30 seconds. Yay! I can use both programs on one machine again! (Windows XP Professional/Access 2003/Access 2007)

It installed fine on my Vista machine, but I'm disappointed to see that editing a query simply by resizing a column in an access 2000 mdb file corrupts the file such that it can no longer be opened in access 2000. Unfortunately, that's a bit of a show stopper for me.

Have found that one of the files I was attempting to open is now corrupted. Access tells me I need to delete the VBA project. Joy. Windows Vista Home Premium / Access 2002/ Access 2007.

Alan: It seems like you've got something strange going on in your system. We definitely tested your scenario, and it worked well under our test environments. Your experience is definitely not something we have seen, at least not on the Access team. Would you send me mail so that we can follow up? Anthony: Could you answer a couple questions? 1) What do you mean by 'corrupt'? That word is usually used to describe a document with invalid binary code that can no longer be loaded and run correctly by any version of Access. If I understand correctly this file still works in 2007 (please let me know if this isn't the case). 2) If you're reading and editing a file in the 2000 file format, you should have no problems editing queries. Would it be possible for you to send me an email with detailed reproduction steps that you know cause this behavior, and describe the expected and actual results?

Zac,

After 7 hours of fiddling around with installing Access 2007 and the SP and trying System Restore (it failed), I uninstalled my Access 2002 then uninstalled Access 2007 followed by reinstalling Access 2007 (it worked) and then the SP, which worked. Oh the relief... Pity I can't use Access 2002 on my PC now, but I'll settle for what I have got and will design stuff in Access 2007 followed by testing using Virtual PC before sending any .mdb's to my clients. I'll send you an e-mail with a more structured explanation of what happened today. Alan

Khuzema: download.microsoft.com/.../Office%202007%20Service%20Pack%201%20Changes_all.xls

linked from

support.microsoft.com/.../936982

Noted that SP1 patched the issue with date modified timestamps not being updated on form and report design. That's great news. But a major roadblock for me in deploying an Access 2007 (ACCDB) version of my applications has been the issue of reports losing their specific printer setups (reports always revert to default printer). I was hoping for a fix in SP1. Can you give us any news on a timeline for fixing this problem? Thanks for any info. Gary

Hi Zac,

Is there any solution for my issue? SP1 doesn't fix it. Here it is:

www.access-programmers.co.uk/.../showthread.php

"If you assign the Control Source of text boxes in Report_Open, you may crash Access 2007 if the report is more than one page long. (Similar to kb 927536, but is issue not limited to Layout View.)" This mega-bug is patched by SP1? Bye