J
John
Hi. I am a first time user, using InfoPath to manage forms for a client.
My client has about 30 users and 20 products. Each users has access to
between one and three products.
The data collected for each form is identical and will be stored in an SQL
Server db. There are only be minor text changes to a few labels based on the
Product Name. (And possibly a different gif for each product logo.)
I am trying to get a feeling for maintenance and contention issues. If I
build one form for each of my 20 products, I will have 20 forms to maintain
for each change, but there will be less contention between users.
If I build 1 form to handle all my Products, there is slightly more complex
design tasks, less maintanence but it seems to be more potential for
contention between concurrent users.
The real issue that I do not understand is contention. Should I build one
form for each Product? Any thoughts are greatly appreciated!
Regards,
John
My client has about 30 users and 20 products. Each users has access to
between one and three products.
The data collected for each form is identical and will be stored in an SQL
Server db. There are only be minor text changes to a few labels based on the
Product Name. (And possibly a different gif for each product logo.)
I am trying to get a feeling for maintenance and contention issues. If I
build one form for each of my 20 products, I will have 20 forms to maintain
for each change, but there will be less contention between users.
If I build 1 form to handle all my Products, there is slightly more complex
design tasks, less maintanence but it seems to be more potential for
contention between concurrent users.
The real issue that I do not understand is contention. Should I build one
form for each Product? Any thoughts are greatly appreciated!
Regards,
John