MartyConnelly
martyconnelly at shaw.ca
Thu Nov 20 14:32:32 CST 2003
Where this is leading, I am not sure but here are some things, you can do with InfoPath. --------- Here is one way of getting speed out of xml files try using with InfoPath If the methods are followed you may get a retrieval time 10 times that of SQL Creating an In-Memory Database Using XML and XPath -- Part 2 http://www.15seconds.com/Issue/010410.htm?voteresult=5 ---------- downloaded the InfoPath SDK, and try to use the ADO sample form and access database that MS has provided. However, one caveat that messed me up If you search inside manifest.xsf you will see that the reference to Infnwind.mdb is relative. So the published form template expects to find Infnwind.mdb in the same directory as you published the form template to. But the Access database isn't there. If you copy it there your problem should be solved. Copy Infnwind.mdb to the shared folder. InfoPath SDK http://www.microsoft.com/downloads/details.aspx?familyid=351f0616-93aa-4fe8-9238-d702f1bfbab4&displaylang=en --- Try viewing the .xsn or .mht file in IE. ------- You should be able to access web services from InfoPath. ------- Gustav Brock wrote: >Hi Martin > >I agree with Charlotte - he makes it sound like InfoPath is a >no-product? > >And this scares me: > > > >>.. If you are not familiar with relational databases and tools like >>Access, then InfoPath is a tool to consider if your business is starting >>to adopt XML as a transport mechanism between business processes. >> >> > >I mean, if you are not familiar with relational databases, you don't >know about a relational structure and, thus, you should stay away from >even thinking of transferring data by any means including XML as you >don't have a chance to know what you are doing. > >Of course, you can move around with a Word document saved as XML but >that has little to do with moving data between business processes. > >/gustav > > > >><quote> >> >> > > > >>I try to dispel the marketing hype around InfoPath for the Access developer. >>I've yet to see an InfoPath >>scenario that couldn't be solved quicker with Access 2003 and its new >>XML features. If you are not familiar with relational databases and tools >>like >>Access, then InfoPath is a tool to consider if your business is starting >>to adopt XML as a transport mechanism between business processes. >> If you live in a world of ODBC and OLEDB for moving data within your >>organization - and it's working - why mess with a good thing. On the >>other hand, if you are struggling with ways to send that data through >>your firewall to your business partners/customers, XML works really >>well, because text doesn't get hung up in the process. With that said, >>Access is an excellent tool for exporting relational data as XML and >>importing XML from other sources. >> >> > > > -- Marty Connelly Victoria, B.C. Canada