InfoPath Dev

Hello everyone.  I am working on my first ever project with SharePoint and InfoPath and I have hit a brick wall.  I was hoping someone would be able to help me out. I have created a series of five SP lists that contain both "lookup" columns and entered text.  I want to create a form using InfoPath that will creating ...

[quote user="Jimmy"]No, I don't think there's anything as simple as what you're asking about, but this should work for getting the first 6 words of a string: substring(field, 1, string-length(field) - string-length(substring-after(substring-after(substring-after(substring-after(substring-after(substring-after(field, " ...

I know how to run it in in debug I had been up for 15 hours and exhausted, I did not see the line 76 on my screen as I was remotely connected until I posted. I changed my code and fixed the error. Thanks for the reply.           

This worked perfectly - and it made sense.  Thank you for your help! Note:  Would be great (if it is possible) in a future iteration of InfoPath, the AccountId can be promoted as a people field in Sharepoint.

Qrules embedds code in your template/form(.xsd)  It eases some of the custom code development.  I find I can accomplish most of what I want without add my own code.  Basically a function library.  An enhancement for the form development. DBXL process the resulting documents/data (.xml) generated by your template/form ...

Can someone at Qdabra give be a quick overview of the tools you guys offer. Mainly, Database Accelerator and qRules. I couldn't find a comparison on the product pages. I saw and tested Database Accelerator already and like the ease of what it does but have not gone too deep into it. However, I understand you guys have qRules which does the ...

Activate NonAdminSolution failed with unhandled exception System.TypeLoadException: Method 'get_ServerInfo' in type 'Microsoft.Office.InfoPath.Server.SolutionLifetime.XmlFormProxy' from assembly 'Microsoft.Office.InfoPath.Server This is the error im getting Thanks

I would suggest trying to fill out all of the tab indexes with proper values to see if that fixes your problem.

The end result should be "Represents text that should be kept". So it should print 6 words instead of 6 characters.

Yup, that's a pitfall for this. Off hand, the only thing I can think of is some kind of hidden button and then just train the users - have a button on the form that is basically invisible (upper left corner or something) that they can click in this instance. There really is no good UI way to handle the cancelling of an email submit.