Office 2010 Technical Preview Ships

re: Office 2010 Technical Preview Ships

Andrew Couch — Tue, 21 Jul 2009 10:34:51 GMT

Renaud Bompuis said: "It seems to me that upsizing is going to become a lot more complicated unless there are good tools that can convert these new macros into equivalent behaviours." As a third-part tool vendor for upsizing products we will most certainly be looking into how all the new features in 2010 can be converted to equivalent features in SQL Server. So there will be people out there focused on these issues.

re: Office 2010 Technical Preview Ships

Craig Alexander Morrison — Tue, 21 Jul 2009 08:49:00 GMT

Renaud Bompuis said: "I like the idea of these calculated columns and macro 'triggers', even though I understand that they offend some database purists." Actually as long as the data redundancy is managed at the engine level they would conform with the model.

re: Office 2010 Technical Preview Ships

Craig Alexander Morrison — Tue, 21 Jul 2009 08:44:48 GMT

grovelli said: "What made you change your mind?" Well I am still going to defend the relational model on which Access (up to 2003) is loosely based. The implicit relationships hidden in the MVF in ACE are a dangerous departure, which may or may not have been exposed in the next version of ACE. I will continue to lurk in case Access ever gets back on the right path, but I am not holding my breath.

re: Office 2010 Technical Preview Ships

Renaud Bompuis — Tue, 21 Jul 2009 06:40:36 GMT

I've been playing around a bit with the preview.

Some of nice new things in there. I like the idea of these calculated columns and macro 'triggers', even though I understand that they offend some database purists. Pragmatically, they can be useful and will solve a lot of real-world problem for power-users. The issue I see now with these enhancements is how they will affect moving an Access back-end that rely on them to SQL Server. It seems to me that upsizing is going to become a lot more complicated unless there are good tools that can convert these new macros into equivalent behaviours. Too early to tell probably. The area that I find most disappointing is the VBA where I cannot see anything new or enhanced at all.

I guess we're going to stay stuck in 2001 for a while with this.

re: Office 2010 Technical Preview Ships

Joseph Dowski — Mon, 20 Jul 2009 19:04:38 GMT

I too would be very interested to see if Access could get over it's existing 2GB mdb file size limit. While you can certainly break up large databases into multiple back ends, a new size limit of even 5GB would make that unnecessary in all but a few of my largest DBs....how about 10GBs ?? ;) J.

re: Office 2010 Technical Preview Ships

grovelli — Mon, 20 Jul 2009 18:31:24 GMT

Welcome back Craig :-) What made you change your mind?

"Another old dinosaur signing out, goodbye y'all."

re: Office 2010 Technical Preview Ships

Craig Alexander Morrison — Mon, 20 Jul 2009 17:57:42 GMT

"(I'm thinking of the 255 column limit more than the 2GB limit here.)" There is (almost) NO table in the universe that would need anything like 255 columns. In a properly normalised relational database design.

re: Office 2010 Technical Preview Ships

John Rylander — Mon, 20 Jul 2009 17:03:45 GMT

Are there any significant changes in system limits? E.g., can databases be more than 2GB now? Can there be more than 255 fields? It's a shame to have to rely on slow-but-capable Excel to present a huge amount of specified information for the user to browse/filter dynamically. (I'm thinking of the 255 column limit more than the 2GB limit here.)

re: Office 2010 Technical Preview Ships

Alan Cossey — Sun, 19 Jul 2009 21:20:16 GMT

Clint,

Thanks for your reply. I look forward to the public beta later! Alan

re: Office 2010 Technical Preview Ships

Clint Covington — Sat, 18 Jul 2009 23:34:35 GMT

@sevenflavor - the fact it is missing from the ribbon is a bug. We have fixed it in recent builds. You can get to all the commands in the outspace/ | Options | customization command well if you have short term needs.