You can use your favorite social network to register or link an existing account:
Or use your email address to register without a social network:
Sign in with these social networks:
Or enter your username and password
Forgot your password?
Yes, please link my existing account with for quick, secure access.
No, I would like to create a new account with my profile information.
Web databases introduced a few ribbon design challenges, particularly how to present client and web create options? We wanted to make sure that people creating client objects are just as successful as web objects.
When you create a new database from scratch, you have two options: either to open a blank database or a blank Web database.
Creating a new blank Web database opens a new database that allows you to create both Web and Client objects. Client objects have the full designers and ability to include VBA whereas the Web object designers enable you to build tables, queries, forms, reports and macros that can run on the Web and take advantage of the functionalities of Access Services. The Create ribbon makes it easy to create Web objects by selecting any of the top level options. Client objects can be created by selecting the options in the Client Forms, Client Reports and Client Objects dropdowns.
Creating a new blank database opens a new database that has the full designers. Any form, report, query or macro you create in this database cannot run on the Web. This Create ribbon is below and gives all the Client objects you can create.
You can still publish the database to Access Services. You do this by going to the File tab, going to the Save & Publish tab and selecting the Publish to Access Services option. Once the database passes compatibility checker and publishes, you can create Web objects to bring parts of your database to the Web. At this point, the ribbon changes to the Web database ribbon that optimizes entry points to create Web objects.
There will be a few changes coming after Beta 2… For book authors interested in how the Create ribbon will look when we ship Access 2010, you can reference the ribbon below.
Enjoy!
Comments: (9) Collapse
Still waiting for Web Services...
I am in love with MS Access 2010 and its excellent WEB SERVICES. You have done a lot with the new version of MS Access. What scares me is its requirement. MS Sharepoint 2010: "so today we’re happy to announce (and confirm) some preliminary system requirements for SharePoint Server 2010: 1- SharePoint Server 2010 will be 64-bit only. 2- SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2. 3- SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005. " As I am not interested in Hosted version, I will have to stick to FE/BE setup and use Tony "Auto FE Updater utility " and wait 3 more years for MS Access 15. By the way you could incorporate this very good FREE utility in MS Access 2010. Joao Santos
I totally agree with Joao Santos. Pride comes before the Fall. Sharepoint team should not sit as database guru but act as the servant of consumers. MS Sharepoint 2010: "so today we’re happy to announce (and confirm) some preliminary system requirements for SharePoint Server 2010: 1- SharePoint Server 2010 will be 64-bit only. 2- SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2. 3- SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005. " This is stupid. I will use Access 2010 only.
Joao--I'm curious why you aren't interested in a hosted version. Is this just not relevant to your scenario or do you have other reasons?
Joao: Is this what you're talking about?
en.wikipedia.org/.../Web_service To me SharePoint is of no interest.
Thank you for your reply. I like all the new features of MS Access 2010 (macros, navigation UI etc..). I want to try its Web Services because looks like that implementation of database would be easier. I am not interested in Hosted version because our database, used by 8-10 PC, keeps confidential medical records and I am afraid of "taking" them out of office... I will try to install MS Sharepoint 2010 BETA here in my office in one free PC. Its requirements scares me a bit. Do I need Windows 2008 Server 64 bit+ MS SQL Server 2008+ MS Sharepoint 2010 just to use MS Access Web services? Thanks once again. Joao Santos.
>Still waiting for Web Services... I don't think you understand how SharePoint works. Just about everything in SharePoint is exposed as web service. In fact, you can think of sharePoint as really a collection of web services that you can use. You can certainly write rich desktop applications that consume web services. It really going to be a question of what development platform, or so called development stack you adopt here. Here is a list of SharePoint web services that is for SP 2007, but I guessing the web services for 2010 is going to be much larger.
msdn.microsoft.com/.../ms479390.aspx I kind of confused here by your question? The whole design of SharePoint is really very much based around web services. I suppose it is WAY too big a can of worms to open here, but I am most curious if the access services in SharePoint will be exposed as web services that .net developers can consume? My guess is likely yes and I don't see why access services would not be exposed like near every other part of SharePoint that is a web service now....
Can we make the font's and icons smaller to get more developer space like Visual studio?
Albert: I need to cooperate with existing web services which are not based on SharePoint. SharePoint solution seems to be VERY EXPENSIVE and I'm sure our custumers won't go that way. And I can't expect that existing web solutions will ever be moved to SharePoint - there is no reason to do it: they work fine and they don't need to to be moved to a new unknown technology (SharePoint).
Comments: (loading) Collapse