I'm working on a database that is going to be pushed out wide and far. The question is, what is the best way to do that. Issues:
- I don't think a standard FE/BE split will work because there is not a common shared drive.
- The company already uses SharePoint. And, I think there are SQL servers that everyone has access too (assume so for this discussion).
- It will be difficult for me to push updates out to users because of not sharing drives; I'm not thrilled with the idea of doing it by email.
- Related, I'm a contractor and won't be here to maintain the system (or to push updates out). I'd want a stable environment.
- Most will have read-only access. A few will need to be able to edit data.
- Some of the back end tables might be come from other systems via ODBC.
- I haven't worked in either SharePoint or SQL Server. I assume (hope) they will be comparably relatively easy for me to transition to from Access.
Thanks,
Adam
__._,_.___
Posted by: runuphillracing@yahoo.com
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (1) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar