|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Hello Group,
I will be joining a project that is already in motioin which has selected
InfoPath as the input form to an SQL Server DB. The InforPath "designer" has
explained to me the reason they determined to use InfoPath yet I feel I have
missed something.
From what I can determine they have an InfoPath form that uses the SQL Serve
to populate some pulldowns. The save the form (several copys I might add)
into a common drive. Lastly, a human takes the InfoPatch form and converts
it to a MDB so that the MDB can be loaded back into the SQL Server.
HERE is my question:why. From what little i understand about InfoPath, it
can be a frontend to a database, right? They told me they like the idea of
saving the file. But if you do this, you have this extra step of moving the
data into an MDB.
Is there anything on the Microsoft site you recomend I read that show in a
block diagram, alternate ways to use this product? It must be a block
diagram because I have to sell this idea to managers that their current use
of the product is not the best.
rich
|
|
|