It should help to discuss some basics and terminology because this can get very confusing.
Access SharePoint Lists are a feature of Access 2010. They cannot be created using Access 2013.
Access Services are a feature of Access 2010 that can only be created using Access 2010 but they can also then be used by Access 2013.
Access Web Apps can only be created by Access 2013 using SharePoint 2013 which can be provided by Office 365 IF that edition of Office 365 has SharePoint 2013. SharePoint 2010 will NOT work with Access Web Apps.
Access Services (2010) saves virtually everything in a SharePoint 2010 Server.
Access 2013 Web Apps saves virtually everything in an Azure SQL Database or a SQL Server Database. But the web app web pages are built on SharePoint Server. To use a SQL Server Database it must be SQL Server 2012 and you must use your own installation of SharePoint 2013. Otherwise you use the SharePoint 2013 provided by Office 365 and your tables and schema are saved in an Azure SQL Database.
>can an Office 365 database have tables that are linked to an SQL server here in my server room?
One way to do this is by using Access 2010 and using ODBC linked tables you have migrated to SQL Server. You can then use Access Services with Access 2010. Your tables will then exist in both your SQL Server database and in SharePoint.
http://dmoffat.wordpress.com/2009/11/06/access-2010-and-sharepoint-welcome-to-the-hybrid-access-application/
Also if your company has it's own installation of SharePoint 2013 and you use Access 2013 you can save everything in a local SQL Server Database when you create a web app.
http://msdn.microsoft.com/en-us/library/office/jj250134%28v=office.15%29
>Secondly, I have used natural keys for primary keys in most of my databases. It looks like I'm in big trouble since the compatibility checker says I need a PK with a number and long for compatibility. I'm open for suggestions here.
Yes that is true with Access 2010 if you publish to SharePoint or Access Services. With Access 2013 the ID field is created for you when you create your table in Access.
>And I remember reading many posts that indicate that web databases can't run VBA code. Does that apply to Office 365?
You can run VBA in Access 2010 on the database on your local computer while connected to SharePoint and Access Services. This is called a hybrid database.
But you cannot use VBA with Access 2013 web apps because everything runs on the web page. You therefore must use Macros which are much improved and have a very effective set of features that enable you to use If...Else...Then constructs and loop through all the records in a table or query much like using a recordset. But you can use VBA in the local computer's Reporting Database which you create so you can develop and use Reports in that database.
You can create a Reporting database for the web app that runs on your local computer only. Reports do not work online in Office 2013.
Patrick Wood
Founder, Gaining Access Technologies
http://gainingaccess.net
--- In MS_Access_Professionals@yahoogroups.com, Jim Wagner wrote:
>
> I read this morning that the Access and Publisher applications are not web based. It looks like they are local applications
>
> http://content.webcollage.net/apps/cs/mini-site/systemax/module/msofficefifteen/wcpc/1353556794555/tab/faq-16583b49?enable-reporting=true&showtabs=&channel-product-id=7539170
>
>
>
> About the new Office
> * Which Office products are available for home and business?
> New products are being released for home and business use. The products listed below may be used at home or at a small business, depending on license restrictions.
> Office product Where can I use it?
> Office 365 Home Premium At home
> Office Home and Student 2013 At home
> Office Home and Business 2013 At home or for business use
> Office Professional 2013 At home or for business use
> Word 2013
> Excel 2013
> PowerPoint 2013
> Outlook 2013
> OneNote 20131
> Access 20131
> Publisher 20131 Office applications can be bought as standalone products, or as part of an Office 2013 suite or Office 365 plan. Usage rights vary according to the exact product purchased.
>
> 1
> Access and Publisher available on PC only. OneNote not available on Mac OS.
>
> .
> Â
> Jim Wagner
> ________________________________
>
>
>
> ________________________________
> From: dnwinberry
> To: MS_Access_Professionals@yahoogroups.com
> Sent: Wednesday, January 30, 2013 9:52 AM
> Subject: [MS_AccessPros] Access 2010 and Office 365
>
>
> Â
> Hello friends,
>
> I just found out that my corporate IT department will be rolling out Office 365 this year. I've done some initial checking but that looks like its going to be big problem for me and I have some questions. First of all and most importantly, can an Office 365 database have tables that are linked to an SQL server here in my server room? Secondly, I have used natural keys for primary keys in most of my databases. It looks like I'm in big trouble since the compatibility checker says I need a PK with a number and long for compatibility. I'm open for suggestions here. And I remember reading many posts that indicate that web databases can't run VBA code. Does that apply to Office 365?
>
> Thanks!
> Doyce
>
>
>
>
> [Non-text portions of this message have been removed]
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (4) |
Tidak ada komentar:
Posting Komentar