InfoPath Dev

I'm hoping that in the 2005 version of InfoPath they allow us to use relative paths for sec data source.

this works myLocationOffloadCode = e.Parent.selectSingleNode(''../@LocationOffloadCode'') but it produces error msg for every other record returned. It does function correctly, as far as I can see--I set the LocationOffloadCode to Nothing, and only that record gets set. I can turn off the error message popup in the try statement and be ...

+ Me {OffloadRequestReview.OffloadRequestReview} OffloadRequestReview.OffloadRequestReview - e {Microsoft.Office.Interop.InfoPath.SemiTrust.DataDOMEventWrapper} Microsoft.Office.Interop.InfoPath.SemiTrust.DataDOMEvent + [Microsoft.Office.Interop.InfoPath.SemiTrust.DataDOMEventWrapper] {Microsoft.Office.Interop.InfoPath.SemiTrust.DataDOMEventWrapper ...

Looking in the debugger, both e.source.parentnode and e.parent resolve to 'nothing' I seem to be able only to get the value of the first record returned. So, neither of these suggestions are working.. e.Source.parentNode.selectSingleNode( ''@LocationOffloadCode'' ); Depending on what e.Source points to you might have to ''normalize'' the source ...

A good solution would be to use Sharepoint, but they are having trouble getting it to work because of the narrow bandwidth. Unfortunately, someone in marketing had the bright idea of selling VoIP to the crew and passengers as a new revenue stream, and that eats all bandwidth 24/7. Unfortunately, a lot of the problems are politically caused, not ...

Thanks, that worked perfectly. Now I just need to select the right row to change working..neither of the suggested code above worked, so I need to play around with it until it returns a value.

Can't send the XSN files through email for two reasons. 1. all executable files blocked in email, no exceptions. 2. They are way too big for the narrow bandwidth pipe. I am breaking down the larger XML data sources into smaller ones so the updates are smaller. One of the other main problems with all the data files local on each client is that ...

Yeah, my code is in the first message. OnAfterChange fires twice for each record returned from the query. I can use e.Operation = ''Insert'' to filter out half the firings, but I really need to filter out ALL the firings for the initial query return, and catch only one when the user changes the value.

The sites have intermittent Internet access on small bandwidth channels --they are cruise ships. The forms are installed from cd, and all data is sent via email, both directions. Secondary data is updated by sending XML files to each client via email. Form data is sent by email directly to the SQL Server to be bulk uploaded. All forms have full ...

When your major corporate clients request reusable code that their people can use for Office automation, it's gonna be VB.Net. If I was still working back at Microsoft, I'd be using C#. Being a long term Microsoftie, I would never touch anything related to java(not a bad language, just too much bad history). Never could understand why they chose ...