• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 605
  • Last Modified:

Updating SharePoint 2007 List usingn Access 2007

I am very new to SharePoint.  Management wants a process visible on SharePoint as quickly as possible.  We created a native serial workflow in SharePoint and the lists are connected to Access fine.  Is it possible to use Access to update the status field of the tasks to trigger SharePoint that the task has been completed and the next task in the workflow can be assigned?  I can change the Status field and the % Complete field to Completed / 100.00% but SharePoint logs the following error then rolls the record back to the previous values.

The task was marked as completed but no approval or rejection choice was made.

There is an Outcome field in the History list that SharePoint updates with Approved/Rejected but the field is locked in Access and I can't change that one.

Is there any other way around this or is this a constraint with native SharePoint workflows?

Thank you!
  • 2
2 Solutions
As I understand you have connected to a "TASKS" list on which workflow is creating the tasks. You would like to mark the task complete to make the workflow move forward, am I right? If so then you cannot trigger it from Access - workflow creates a special ASPX page on which you need to click "Completed" to let the workflow know the task is completed.

You could make a workaround - do not use tasks instead use the "Wait for field change" activity. This way workflow will wait for the current item's specific field change (for example "Approval status") and move forward once it has been changed.

BTW Why do you want to work from Access?
greenprgAuthor Commented:
We already have our process programmed into an Access database but management wants the visibility of having it hooked into SharePoint.  The database already collects data and creates reports, etc. so we were hoping to hook Access into some simple native workflows to get it up and running soon.  Since there is data we are collecting through the database, if we can trigger the workflow from Access, it would save the user from going into both applications.  We were hoping to keep the process the same for the users but link in SharePoint to do the e-mail notifications and management could use SharePoint to see where things stand.

If you think your workaround above could work OK for this, can you send a few more details?  How do I change the native workflow to "Wait for field change"?  

greenprgAuthor Commented:
Thank you for you effort.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now