Access 2013 web apps without Sharepoint?
Can Access 2013 be used to make apps usable from a browser without Sharepoint?
There's lots of hype about its ability to do this in Sharepoint.
There's lots of hype about its ability to do this in Sharepoint.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
<Just hoping that the Access Web hype might actually make things easier without big investments.>
Yes, I know of a few people who have done this...
But it is not as easy as just making a standard DB and clicking the "Load to Sharepoint" button.
;-)
- You have to build a Web database specifically (that has a lot of design differences and limitations than a standard Access database)
- You have to buy, and maintain Sharepoint.
I had held out hope that Access 2013 might have a way to put an "existing" db up on the web a little more painlessly...
JeffCoachman
Yes, I know of a few people who have done this...
But it is not as easy as just making a standard DB and clicking the "Load to Sharepoint" button.
;-)
- You have to build a Web database specifically (that has a lot of design differences and limitations than a standard Access database)
- You have to buy, and maintain Sharepoint.
I had held out hope that Access 2013 might have a way to put an "existing" db up on the web a little more painlessly...
JeffCoachman
Let's clear up some confusion here.
In A2010, the 'web' side of the product is called Web Databases. The back end is Sharepoint Lists.
In A2013, the 'web' side of the product is called Web Apps. The back end - where your data really resides - is a REAL SQL Server database. And it's not hype. It's a completely different different, and much improved paradigm.
Sharepoint is still part of the mix, but only plays an 'administrative' role in the paradigm, where you setup and configure various items (users, permissions, etc) for Web Apps. Sharepoint has zero to do with storing data in A2013.
"I had held out hope that Access 2013 might have a way to put an "existing" db up on the web a little more painlessly... "
Whereas this is still not possible yet in A2013, it's a LOT closer than A2010. Using the A2013 web UI (as opposed to desktop), you can 'import' and upload your Tables from an Access DB to SQL Server. When you do this, Access automatically creates two view for your tables ('List' and 'Datasheet') - which are then available in a browser - one you log into your 'Sharepoint' site. And if you have straight forward Relationships between tables - for example One to Many (Customers>>Orders), Access will keep those in tact - and create the 'Many' view related to the 'One' view.
This gives you a decent jump start toward 'converting' you db into a Web App - with ** a real SQL Server backend **. And of course, from here, you can customize what Access has created for you , as well as build your own views etc. Whereas you still cannot run VBA code, Data Macros have gotten better in A2013, and it turns out you can do some pretty powerful stuff.
I've been testing an app with a million records - and the web performance is nothing short of amazing.
"The "Web Databases" in Access are designed to work with Sharepoint."
Jeff ... this (as described above) is not really the case per se in A2013.
"Just hoping that the Access Web hype might actually make things easier without big investments."
You can. Now that Office 365 has gone live with the 2013 version, you can for as little as $6/month setup an Enterprise account to host your web apps.
Further, it's possible to have your own domain address associated with your account, as well as anonymous connections and so on. Much of this is just evolving as we speak.
I've barely scratched the surface here ... and left a LOT out. Microsoft is making a HUGE investment in Web Apps and this is where it's headed. You might in some ways think of this as akin to Access 2.0 in a certain sense - the state of where A2013 Web Apps are - minus VBA code.
I suggest you start Here ... and search on Access 2013 as well as Data Macros. You will find approx 30 KBs on the subject - that will help get you up to speed.
mx
In A2010, the 'web' side of the product is called Web Databases. The back end is Sharepoint Lists.
In A2013, the 'web' side of the product is called Web Apps. The back end - where your data really resides - is a REAL SQL Server database. And it's not hype. It's a completely different different, and much improved paradigm.
Sharepoint is still part of the mix, but only plays an 'administrative' role in the paradigm, where you setup and configure various items (users, permissions, etc) for Web Apps. Sharepoint has zero to do with storing data in A2013.
"I had held out hope that Access 2013 might have a way to put an "existing" db up on the web a little more painlessly... "
Whereas this is still not possible yet in A2013, it's a LOT closer than A2010. Using the A2013 web UI (as opposed to desktop), you can 'import' and upload your Tables from an Access DB to SQL Server. When you do this, Access automatically creates two view for your tables ('List' and 'Datasheet') - which are then available in a browser - one you log into your 'Sharepoint' site. And if you have straight forward Relationships between tables - for example One to Many (Customers>>Orders), Access will keep those in tact - and create the 'Many' view related to the 'One' view.
This gives you a decent jump start toward 'converting' you db into a Web App - with ** a real SQL Server backend **. And of course, from here, you can customize what Access has created for you , as well as build your own views etc. Whereas you still cannot run VBA code, Data Macros have gotten better in A2013, and it turns out you can do some pretty powerful stuff.
I've been testing an app with a million records - and the web performance is nothing short of amazing.
"The "Web Databases" in Access are designed to work with Sharepoint."
Jeff ... this (as described above) is not really the case per se in A2013.
"Just hoping that the Access Web hype might actually make things easier without big investments."
You can. Now that Office 365 has gone live with the 2013 version, you can for as little as $6/month setup an Enterprise account to host your web apps.
Further, it's possible to have your own domain address associated with your account, as well as anonymous connections and so on. Much of this is just evolving as we speak.
I've barely scratched the surface here ... and left a LOT out. Microsoft is making a HUGE investment in Web Apps and this is where it's headed. You might in some ways think of this as akin to Access 2.0 in a certain sense - the state of where A2013 Web Apps are - minus VBA code.
I suggest you start Here ... and search on Access 2013 as well as Data Macros. You will find approx 30 KBs on the subject - that will help get you up to speed.
mx
ASKER
Thanks.