Portability

[Clayman]

Since InfoPath is XML-Based, what keeps the forms bound to the application?

InfoPath is an awesome tool for developers - creating a simple user
interface. But everything I read says that people can only use it if the
application is installed on their PC. This really kills a lot of the
usefulness of the application.

Currently, I'm working for a client who refuses to upgrade from Office 2000,
and does not want to give everybody carte blanche use of Access. That means
I'm now limited to creating forms in Excel or standalone VB. A portable
InfoPath form would save the day for me, and save money for my client.
--
Adios,
Clay Harryman

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...964-2e295ad89cad&dg=microsoft.public.infopath

 

[Clay Fox]

Hey Clay.

To me best practice is having a central server, typically enveryone needs to
share data and access, excel, etc do not lend themselves to this.

SQL Express is free or SQL 2000/2005 on a server is the answer. Store the
data there and then let them use excel or infopath or whatever to view the
data on their desktops.

InfoPath 2007 has the ability to be displayed in a browser. We also have a
forms server product that is very inexpensive that will work with 2003 too
and display a form in a browser if the clinet does not have InfoPath.

Go to http://www.qdabra.com and check out the Database Accelerator web suite.
--
Thanks

Clay Fox

Qdabra Software
http://www.qdabra.com

InfoPathDev.Com
The Largest InfoPath Forum in the World
http://www.infopathdev.com