Introducing Access 2013

re: Introducing Access 2013

Martin Tallett — Sat, 18 Aug 2012 09:02:49 GMT

Love the SQL Server Azure and Access Integration, coolio ...

re: Introducing Access 2013

Cees Monden — Wed, 15 Aug 2012 18:38:17 GMT

Hi Todd,

I am very dissapointed no support will be given on adp's. I am an access/sql developer respresenting over 1500 employees in the company I am working for, all using adp's (ade's) for different purposes such product workflow, orderings and marketing/sales information and I tried to work with 'pass through queries', but, they do not support @parameters, which we use in thousands of stored procedures so hope you can take this in consideration.

Cees Monden

re: Introducing Access 2013

Gilad1 — Wed, 15 Aug 2012 04:30:19 GMT

Yes I think you are missing something: the revenue that Microsoft is hoping to receive. You wrote that your company has been using 2003 for a decade. Imagine how much $ your company would have payed if it would have been using Office365 all this time in order to use Access+Sharpoint+SqlSever. If I am not mistaken the current cost for this package is 20$ a month (correct me if I am wrong). That accumulates to a lot of money. I think it is fair to make the comparison between these two alternative options. If you compare the web database with 365 and the previous desktop version I think the 365 online will be much more expensive in the long run. I think that it is expensive even if the monthly price doesn't sound like it is a lot. And if you decide to install Sharepoint server and SqlServer locally the prices are even more deterring. Microsoft has every right to try and increase their profit. We all do that and it is perfectly acceptable. But costumers also have a right to try and figure out their costs and expenses.

re: Introducing Access 2013

Dick W — Wed, 15 Aug 2012 02:31:44 GMT

I guess that's one thing that always frustrates me about Microsoft. You guys have drunk so much of your own bathwater that you really believe that customer companies want to be like you and gain the advantages you have with all of this neato technology you develop. They don't. Or at least a lot of them don't. And your own data on migration to new stuff vs. continued use of the old stuff--Off03, WinXP, etc., should show how prevalent this is out there. Companies like mine have had a decade to "get used to the idea of SharePoint apps." They haven't. "No-brainer?" That's giving many of these corporate IT groups way too much credit.

And yes, it appears you haven't "abandoned" desktop databases in the sense that they still open and operate. But I can't find one single thing that you've done in Access 2013 for the desktop database user/developer. Am I missing something? Did you do anything in this release that benefits us? Some of my queries/lookup fileds break for no explicable reason. Beyond that? I'm not seeing any upside in Access2013. Try though I might.

re: Introducing Access 2013

Alan Cossey — Sun, 05 Aug 2012 10:53:41 GMT

Andrew,

Thanks for the reply about web databases. Sounds really good.

re: Introducing Access 2013

Nelson Gonzalez — Sat, 04 Aug 2012 17:30:09 GMT

Could you please elaborate on enhancements to desktop applications support in 2013? I'm specifically interested in unbound forms clients to SQL server backends for ADO and ODBC technologies.

Thank you for your time

re: Introducing Access 2013

Andrew Stegmaier — Fri, 03 Aug 2012 20:41:37 GMT

Robert,

When you wrote of "the SQL-Server that came with access 2013," I'm not sure I know what you mean. To clarify, SQL Server 2012 is a separate product. If you run it yourself on your own servers, you can use it to store the back-end data for a front-end Access desktop database (.mdb or .accdb). In this configuration, you can make databases of practically any size (if you set up your SQL Server machine to handle it). If you have a subscription to Office 365, Microsoft will provision SQL Azure databases for you when you create a new Access 2013 Web database on your SharePoint Online site. You could also, if you wanted to, build a desktop access database and connect to this SQL Azure database for back-end data storage. A 1GB cap currently applies to SQL Azure databases that are provisioned in this way. (You could directly pay for a SQL Azure database yourself, and no such limit would apply).

You are correct, though, that the 2GB limit for traditional desktop databases that store data using JET still exists in Access 2013.

re: Introducing Access 2013

Andrew Stegmaier — Fri, 03 Aug 2012 20:16:46 GMT

Finlay - Details about external data in Access 2013 web databases will definitely be something we'll be covering in-depth in future posts.

re: Introducing Access 2013

rodulio — Fri, 03 Aug 2012 17:57:02 GMT

Yes, I agree that this version does not really address the database size for desktop developers at all and we've been asking for this change since 2000. We are not interested in using SQL because of the workgroup model and definitely not interest in sharepoint either...

re: Introducing Access 2013

FinMtl — Wed, 01 Aug 2012 11:26:50 GMT

As I continue testing the preview it appears that attaching to SharePoint 2010 Lists is not supported but importing them is.

Attachment fields are not supported in the import process.

Why can't the Office team put out a document explaining what is supported.