Access database - desktop and "cloud"
Folks,
I've been presented with an opportunity in developing an Access database for the desktop with the possibility of having it also on the Internet.
For the desktop and land platform - no problem. However, I HAVE NEVER been approached to have the database also accessible from the Internet.
My question what are some of the gotchas I may be facing? Can this be done? Any additional software? I just don't know.
I've been presented with an opportunity in developing an Access database for the desktop with the possibility of having it also on the Internet.
For the desktop and land platform - no problem. However, I HAVE NEVER been approached to have the database also accessible from the Internet.
My question what are some of the gotchas I may be facing? Can this be done? Any additional software? I just don't know.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
with the possibility of having it also on the Internet
For what purpose? Who will be the users? Do you need to allow anonymous users or will every user be known? What functions to the remote users need? Is Citrix/RDP an option? Will you host the app yourself or will you host it at a service bureau. By "Access" do you mean that you want an ACE database as your BE or you want an Access FE?
You cannot make any decision on a course of action with that fuzzy description. People say this all the time because they think that web apps are some how cool and therefore better than client server apps because they are the latest fad. But if all your users are on your LAN, a web app has no advantage and in my opinion has disadvantages. One of which is cost. The cost to develop a web app is significantly higher, usually 3 or more times more and will also take longer than developing an Access client/server app.
If you want to use Access 2013 to develop a web app, you will also need either the latest version of SharePoint running in house or you will need a subscription service. In this case the BE will be SQL Azure, it will NOT be ACE. Access web apps do not support "Access" databases! Your outside users will also be limited so this is not a good option for a public facing app. You also need to keep in mind that Access web apps are limited in functionality. They are restricted to using macros only. No VBA or other programming language is supported. There are other limits to what you can do. No reports for example - NO a web page that goes on forever is NOT a report. So before you get into this make absolutely sure that you can do everything you need to do now and for the foreseeable future.
With an Access web app, you can create a hybrid application where you have a traditional client/server database that includes some web forms published with SharePoint and they all connect to the same SQL Azure BE. If you go the Access web app route, this is probably the most useful option. It will allow remote access to certain features but still retain the user-friendliness of a client/server app for most functions. Don't plan on converting an existing application to a web app. You must build them from scratch although in a hybrid, you can start with a converted app and add the web features. You may need to change the schema though because SQL Azure does not support any of the new data types introduced with A2007 such as attachments, memos, and multi-value fields. SQL Server also does not support hyperlink type fields.
My configuration choice for applications that are used primarily on a LAN but that have some remote users is Citrix. The technology is very stable and doesn't require any changes to the Access app. And, because of the way Citrix works, the Citrix users frequently experience better performance than the LAN users.
ASKER
Pat,
The points you make are great! You're correct about "fuzzy". I have not interviewed the client yet and what the agency sent from the client was vague. They are referring to MS Access 2007 as the development tool and I would challenge that from the very beginning. From what the agency has said the client believes that it should not be a big deal to develop the database then post it to the Internet. Oh, if only that was true. The client also believes that little to no code is necessary. Makes you wonder who they've been talking too? Makes me wonder if I want this assignment?
Thank you
Frank
The points you make are great! You're correct about "fuzzy". I have not interviewed the client yet and what the agency sent from the client was vague. They are referring to MS Access 2007 as the development tool and I would challenge that from the very beginning. From what the agency has said the client believes that it should not be a big deal to develop the database then post it to the Internet. Oh, if only that was true. The client also believes that little to no code is necessary. Makes you wonder who they've been talking too? Makes me wonder if I want this assignment?
Thank you
Frank
Makes me wonder if I want this assignment?From what you said, your best course of action would be ... run fast, and run far.
:)
Or at least make it time and materials. Don't even consider fixed price.
Citrix is frequently the best option when you have remote users. I had one app that ran in Farmington Connecticut and had Citrix users from San Francisco to London and all were happy with performance.
Citrix is frequently the best option when you have remote users. I had one app that ran in Farmington Connecticut and had Citrix users from San Francisco to London and all were happy with performance.
ASKER
Time and material is the only way I'd go with this -
ASKER