Correct Application For Our Needs?

[JESwan]

New to InfoPath, I have built some basic forms connecting to both XML and
Access DB. Seems easy to build forms using the tool, and I like the tool.

However, before I go off and recommend InfoPath as a solution to our issue,
I would like to get some seasoned thoughts from people who have been working
with the product for a while.

Here is what we need to accomplish.

We have a requirement to localize the display and collection of data when
our clients can not connect to the corporate intranet (Have J2EE to do this).
The source of the data is Teradata, we will have to extract data to a
localized Access or XML environment to interact with InfoPath.

Currently we have about 20-25K membership and provider records in our
Teradata environment. I anticipate only having 100 or so membership and
provider records to process at any one time via the local applicatin. That is
the bulk of our data, however there will be other data elements (tables)
which will be displayed and viewed via the InfoPath forms based on the values
of both member and provider ID's from drop down list boxes. These elements
are things like physician visit dates, procedures accomplished, general
notes, confirmation of procedures... These will need to be updated and
captured for re-import back into the Teradata data mart.

In summary, we need to provide our clients with a localized application that
can collect data for specific member and providers. We do not have to
duplicate the web-based app (thank god) only extract, display, collect and
re-import back data elements. Sort of like a screen scrape of data, collected
and re-imported back into the master tables.

We will have about 10-15 indivudual users who will use this localized data
collection approach.

Any thoughts on if InfoPath can scale to this size application.
Any thoughts on the development and maintaince of an application of this size.
~ How will publishing help me if this is a *detached* local application
Any thoughts on XML vs Access as the data source (Pros vs Cons)

As noted my first pass in InfoPath seemed positive, but before I go buy
books and work to build a larger proof of concept, I was wondering if I could
get any input on what we are trying to do.

Details : InfoPath 2003 (Office 2003) SP1 (Should I upgrade)
OS : XP Pro 2002 SP1

As always, Thanks in advance...

Jay

 

[Franck Dauché]

Hi Jay,

Just a few random thoughts here after reading your post:

InfoPath doesn't seem to be the issue here. The problem is to deal with
backend issues such as concurrency. Do you need a check-in / check-out
mechanim to "lock" a particular record when a user is working on it with
InfoPath?

Why are you using Access and not SQL Server at this level?

You should use Managed Code behind your InfoPath form (such as C#). In that
case you need to install Visual Studio .Net 2003 as well as the toolkit for
InfoPath.

You would be better of using Web Services to exchange data with your Database.

Regards,

Franck Dauché

 

[JESwan]

Frank,

Thanks for taking the time...

We anticipate having a flag at a provider record level to indicate the
providers associated records have been taken down to the local level for
process. That way the web-app will not allow any 'flagged' records to be
reviewed via the web-app.

SQL Server for both the main data repository and the localized copy?
We could use SQL Server, the data is currently in Teradata, we could convert
it...

Managed code like C#... Not familiar with this. Can you give me a little
more deatail, and possibly a place to go to understand InfoPath and C# more.

I had seen other postings making mention of Web Services to connect to the
database.
I'll have to explore this more. That would mean our local Infopath page
talks to a local webservice running on the laptop, that connects to the local
RDBMS.

Is this a maintaince issue?

Again, thanks for responding, it has helped alot...

Jay

 

[Franck Dauché]

Hi Jay,

If you didn't start your design yet, look into Managed Code:
http://msdn.microsoft.com/library/d...y/en-us/odc_ip2003_tr/html/odc_INF_Lab_15.asp

Use C# as more code snippets will be available to you and because it will be
easier to get help in newsgroups and forums.

You can connect to an Access DB on the Client side, that's fine. I would
personnally put a Web Service (on the client machine) between IP and the
local DB. Why? Because if you change the DB, you don't have to modify IP
(maintenance may be a pain). In addition, if one day, the data needs to flow
from IP on a server rather than locally, before being submitted back to the
main DB, you will just need to update a connection string in your local WS...

Up to you. In any case, make sure to give Managed Code a try.....

Good luck with your infoPath developments.

Regards,

Franck Dauché