Review workflows converted from data macros
- Thread starter jerem
- Start date
Rx_
Nothing In Moderation
- Local time
- Today, 04:10
- Joined
- Oct 22, 2009
- Messages
- 2,803
One of my complaints about Share Point is the high-overhead of maintenance.
One of the answers is "it depends".
Share Point is great to create data views from databases.
A while back, when working as a Government employee, the managers were all excited about Share Point being used to replace Access for a Regulatory and Compliance DB applications. As the name implies, there were many Rules that had to apply. Bottom Line, after several million dollars and dozens of contractors for over a year (with a 9 month extension), the product never saw the light of day. As Regulations change, the tool became a Tower of Babble maintenance nightmare.
This was pre-Access 2010. But, the contractors were not using Access, they were Share Point programmers.
http://www.codemag.com/article/1301021
Last week, I was researching how much effort to put into Share Point design vs just expanding my TSQL experience. This is a quick article on Share Point Workflow. It does look as if there are some new enhancements. Sorry, it doesn't mention Access.
It does mention how the new model is not comparable with older versions.
The UTTER ACCESS web site does have more Access Sharepoint discussions.
If you find an answer, please be encouraged to share it.
One of the answers is "it depends".
Share Point is great to create data views from databases.
A while back, when working as a Government employee, the managers were all excited about Share Point being used to replace Access for a Regulatory and Compliance DB applications. As the name implies, there were many Rules that had to apply. Bottom Line, after several million dollars and dozens of contractors for over a year (with a 9 month extension), the product never saw the light of day. As Regulations change, the tool became a Tower of Babble maintenance nightmare.
This was pre-Access 2010. But, the contractors were not using Access, they were Share Point programmers.
http://www.codemag.com/article/1301021
Last week, I was researching how much effort to put into Share Point design vs just expanding my TSQL experience. This is a quick article on Share Point Workflow. It does look as if there are some new enhancements. Sorry, it doesn't mention Access.
It does mention how the new model is not comparable with older versions.
The UTTER ACCESS web site does have more Access Sharepoint discussions.
If you find an answer, please be encouraged to share it.
Thanks! I'll read the article tmrw as it is 1am here in HK.
The reason I'm asking is just that I have an Access desktop application that was built for a split Access BE/FE configuration. Now I need to move those BE table to Sharepoint.
The tables have data macros and my simple thinking was: if Access services transforms data macros into Sharepoint workflows when publishing a web database, I might actually publish my tables as web, access the workflows created by Access services, copy them and paste them in my linked table application. Doing so, I do no have to re-write those data macros in Sharepoint workflows myself (a bit lazy I admit)
The reason I'm asking is just that I have an Access desktop application that was built for a split Access BE/FE configuration. Now I need to move those BE table to Sharepoint.
The tables have data macros and my simple thinking was: if Access services transforms data macros into Sharepoint workflows when publishing a web database, I might actually publish my tables as web, access the workflows created by Access services, copy them and paste them in my linked table application. Doing so, I do no have to re-write those data macros in Sharepoint workflows myself (a bit lazy I admit)
Similar threads
