J
JimS
I'm an Access developer. My client uses MSOffice2007 and MOSS. I have two
projects I want to accomplish. I have never used MOSS before, neither have I
used Infopath (2007) before. I'm reading a book on Infopath, and it seems
straightforward to develop forms, but I need some guidance on how to proceed.
Here's my issues:
.. I don't want to migrate my backend data to MOSS. My client doesn't trust
his IT group, and the app is mission-critical for their department.
.. I want to develop a timesheet form (probably using Infopath...) that runs
in a MOSS workflow to accomplish the work I'm doing in Access now (entering
and validating batches of timesheet lines). This will allow (eventually) the
end user to enter his own timesheets, eliminating a huge cost of processing
the manual timesheets currently entered.
.. Validation of each timesheet entry requires reference tables from my
Access 2007 backend database (which is available in a fixed place on the
client's network.)
.. There is an iterative approval cycle that goes something like this:
.. Client's vendor enters a week's worth of timesheet entries (a line for
each worker/day/workorder combination,) typically comprising a few hundred
rows. System validates workerID and workorder to ensure they're valid and
correct.
.. Client reviews the weekly timesheet entries to verify 40-hour rules,
etc. perhaps sending it back to Client's vendor for correction.
.. Once corrections are complete, Client prints batch reports by vendor
for A/P to authorize payment against the standing Purchase Orders. System
assigns purchase order numbers to each line based on the WorkOrder reference
table.
Now, best case is most of the process is done within MOSS, then finally
transferred as a fait accompli to Access for its records.
Minimal case, timesheet lines are entered on MOSS, then transferred to a new
"import" process within A2007 for "batch" validation.
So, what's the strategy? I have a test MOSS site for my use to set this up.
I feel competent to follow general instructions (develop the form as ... then
pubish it like this...then set up the workflow sorta like this....) or you
can point me to resources. I'm happy to read up and experiment. My client is
really hyped up about this, so she's willing to pay me to learn (she does
trust me....)
Thanks in advance for your help!
projects I want to accomplish. I have never used MOSS before, neither have I
used Infopath (2007) before. I'm reading a book on Infopath, and it seems
straightforward to develop forms, but I need some guidance on how to proceed.
Here's my issues:
.. I don't want to migrate my backend data to MOSS. My client doesn't trust
his IT group, and the app is mission-critical for their department.
.. I want to develop a timesheet form (probably using Infopath...) that runs
in a MOSS workflow to accomplish the work I'm doing in Access now (entering
and validating batches of timesheet lines). This will allow (eventually) the
end user to enter his own timesheets, eliminating a huge cost of processing
the manual timesheets currently entered.
.. Validation of each timesheet entry requires reference tables from my
Access 2007 backend database (which is available in a fixed place on the
client's network.)
.. There is an iterative approval cycle that goes something like this:
.. Client's vendor enters a week's worth of timesheet entries (a line for
each worker/day/workorder combination,) typically comprising a few hundred
rows. System validates workerID and workorder to ensure they're valid and
correct.
.. Client reviews the weekly timesheet entries to verify 40-hour rules,
etc. perhaps sending it back to Client's vendor for correction.
.. Once corrections are complete, Client prints batch reports by vendor
for A/P to authorize payment against the standing Purchase Orders. System
assigns purchase order numbers to each line based on the WorkOrder reference
table.
Now, best case is most of the process is done within MOSS, then finally
transferred as a fait accompli to Access for its records.
Minimal case, timesheet lines are entered on MOSS, then transferred to a new
"import" process within A2007 for "batch" validation.
So, what's the strategy? I have a test MOSS site for my use to set this up.
I feel competent to follow general instructions (develop the form as ... then
pubish it like this...then set up the workflow sorta like this....) or you
can point me to resources. I'm happy to read up and experiment. My client is
really hyped up about this, so she's willing to pay me to learn (she does
trust me....)
Thanks in advance for your help!