InfoPath Dev

I finally got the server portion installed after a lot of problems but when I try to install the Query Builder on my workstation I get that it cannot register a template because it was created in a newer version of Infopath.  Ver 12 which would be Infopath 2007. 

 We only run Office 2003 with no plans to upgrade anytime soon.

 Any options?

Thanks!!!!

Hi there, and thanks for trying our product.

Yes, Qdabra’s Query Builder tool uses the 2007 InfoPath Object Model (OM). Therefore, it is not compatible with
InfoPath 2003. What are you trying to accomplish? Perhaps I can suggest a workaround...

I need to be able to read random individual records from a forms library.  I really do not need to read the XML itself, just some items from the list.  The lists are going to get very large over time so just loading them into listboxes or tables and filtering them will eventually not be an option due to the load time. 

 I have a key field that I need to use to search for multiple records and pull just those records into a repeating table. 

I'm still pretty new to Infopath so my first attempt was to load them into a listbox and the loop thru the listbox searching for what I need but as the listbox is based on a secondary data source (the form library) i'm not having much luck with that.  I have found numerous examples but none of them work for me.

I'm trying to do this as quick and dirty as possible as this is a temporary solution.  Otherwise I would have just done it in SQL with a VB front end but didn't want to spend a lot of time coding. 

Trying to avoid doing anything other than Infopath rules and JS.

 Any ideas would be very welcome!

Thanks for your response!!!!!

Oh yes,  I am using Sharepoint 2007 on the server side.

MOSS 2007 or just WSS 3.0?  MOSS is by default an Office 2007 product, and to have those licenses would mean that you likely have an enterprise agreement, which would include all of Office, not just SharePoint.  Do you know why there is no plan to upgrade to Office 2007, which is far superior and is about to be 1 version old (2003 is soon to be 2 versions old)?

It is MOSS 2007.  And yes, we do have an enterprise license agreement but a survey was done to determine the advantages of Office 2007 world wide for us, (multi-national company) and it was decided that the upgrade was not worth the cost at this time primarily from the learning curve that would have resulted because Office 2007 is different enough. So we will be on 2003 until at least next year sometime.  We also skipped Vista and are still running XP so we may go to WIndows 7 and the next Office version at the same time.

So for now I'm stuck in Infopath 2003.

DBXL itself will work with InfoPath 2003, but QueryBuilder won't. Do you have a separate machine where you could install QueryBuilder, create the queries, and then save them (text)? Then you could use your queries in InfoPath 2003. The problem itself is QueryBuilder, not the web method, so if we can build the query separately, I think you'll be unblocked.

Another option would be for use to share with you the query syntax, and you can try to build it by hand.

Cool,  either would work.  I probably have a standalone machine around here that I can load office 2007 on but if it would be possible to send me the synyax that would probably speed things up a bit.  Maybe depending on how hard the syntax is.  I only need one basic query I believe that will be used in two forms.

I only have the trial version right now but if it works I will plan to purchase for sure.

I have been having major issues with installing the server piece of DBXL on the production server.  It is running Windows 2003 x64 with Sharepoint and SQL x64.  I downloaded the trial x64 but it keep getting that install error "client found repsonse content type" on all but one of the sharepoint services.  I was able to install it fine on my 32bit test server. Any ideas?  I've read on this error but I have the SQL rights that should be needed so I'm a little lost on it.  I trashed my sharepoint install and re-installed it fresh and still get the same thing.

Thanks both of you for your repsones!!!!

Concerning the installation error, can you post the full error message? Also, please check the Event Viewer to see if any Qdabra errors are being logged when installation fails.

For the query, here is a sample syntax:
<query>
 <filter>
  <eq>
   <column name='MyColumn'/><value>value</value>
  </eq>
 </filter>
 <sort>
   <column name='MyColumn2' order='ASC'/>
</sort>
</query>

When you paste it into the webservice, don't use spaces or line breaks. I've added those for clarity.

For further reference on QuerySharePoint, please see:
http://www.infopathdev.com/files/folders/sharepoint/entry33871.aspx
http://www.infopathdev.com/files/folders/sharepoint/entry33873.aspx

Bob, did you get a chance to look in the Event Viewer for the full error message?  Ted

Never mind on my last question.  I found it.  Apparently it will not show up in infopath devlopement if the field is not populated.  After I put some data in the first couple of records then when I tried to build the data connection again all the fields appeared.

 Thanks again!