General

Re: how i can unite group of controls and form code to use it in future projects

Patrick Halstead — Fri, 28 Jan 2011 04:01:38 GMT

you can't auto-install activeX when they open a page - it requires client browser permissions. best thing you can do is send your users the activeX in advance and ask them to install but that's kind of lame since some may not do it. you definitely should just use XTPs. XTPs will work in 2003 but to use them you need to design the form in 2007

Re: how i can unite group of controls and form code to use it in future projects

temp-x — Thu, 27 Jan 2011 20:27:09 GMT

hm..its interesting...if i use web based forms..i must install my activex control on client system previously.. can i do it automaticly when some user is trying open(create) my form in sharepoint portal..

thanks Hilary, i'll research that info.

Re: how i can unite group of controls and form code to use it in future projects

Hilary Stoupa — Thu, 27 Jan 2011 20:14:52 GMT

Right, that's why template parts won't work for you. Here's an MSDN link on creating your own ActiveX control that can bind to InfoPath data....

Re: how i can unite group of controls and form code to use it in future projects

temp-x — Thu, 27 Jan 2011 20:02:10 GMT

eh Hilary..i'm broken...its from that link..

"A template part is a portion of a form template that can be saved for reuse in multiple form templates. A typical template part consists of controls and a data source (data source: The collection of fields and groups that define and store the data for an InfoPath form. Controls in the form are bound to the fields and groups in the data source.) and may also include features such as data connections (data connection: The connection between an InfoPath form and an external data source, such as a database, Web service, SharePoint library, or XML file. Data connections are used to query and submit data.), data validation (data validation: The process of testing the accuracy of data; a set of rules you can apply to a control to specify the type and range of data that users can enter.), and rules (rule: A condition or action, or a set of conditions or actions, that automatically performs tasks based on events and values in the form.). "

there isnt code support(

anyway thank you for your help, tomorrow i'll read that info..may be there is another way..

Re: how i can unite group of controls and form code to use it in future projects

Hilary Stoupa — Thu, 27 Jan 2011 19:54:34 GMT

Given your new example of what you are looking for, perhaps this article will help you.

Re: how i can unite group of controls and form code to use it in future projects

temp-x — Thu, 27 Jan 2011 19:46:53 GMT

yes, you were right=) but i dont understand what do you mean "baseline template"? i just need myown control with code..like searching mehanism to add new user from sharepoint portal (ip2010)

by the way do you have skype?

Re: how i can unite group of controls and form code to use it in future projects

Hilary Stoupa — Thu, 27 Jan 2011 18:59:38 GMT

I think I maybe don't understand what you are trying to do.

I thought what you meant was that you have a general set of InfoPath controls, data structure and code that you want to be able to reuse in multiple templates. Since you need code, template parts appear to not be an option for you. I was suggesting creating a baseline template and using it as a starting point for each new project. But it appears I'm continuing to misunderstand what you are trying to accomplish.

Re: how i can unite group of controls and form code to use it in future projects

temp-x — Thu, 27 Jan 2011 18:23:26 GMT

do you mean that i have to create templates for visual controls only? and then add custom code in specific form?

now i want to exclude custom code to external DLL files (i'v created finding mechanism, common utils for repeating tables, saving form in context web site and ect..) but best way for me is templates with custom code(

Re: how i can unite group of controls and form code to use it in future projects

Hilary Stoupa — Thu, 27 Jan 2011 18:05:36 GMT

If what you are asking is if you can use custom code in template parts, you are correct, you cannot add custom code to template parts. I'd suggest you create a base template that has the controls and code you wish to reuse, and start any new templates using the base template. You can change the form's name under the form properties to prevent name conflicts.

Re: how i can unite group of controls and form code to use it in future projects

temp-x — Thu, 27 Jan 2011 17:40:13 GMT

thank you Hilary, but i'm confused..i can't use myown program code in infopath tempates..am i right?

Re: how i can unite group of controls and form code to use it in future projects

Hilary Stoupa — Thu, 27 Jan 2011 16:52:29 GMT

Template parts came out with InfoPath 2007. You can read more about them here. Don't let the blog title fool you -- even though it says InfoPath 2010, you'll see in the article text they refer to InfoPath 2007: " this new InfoPath 2007 feature called template parts"

Re: how i can unite group of controls and form code to use it in future projects

temp-x — Thu, 27 Jan 2011 15:40:30 GMT

thanks for help, i never heard about that, but what version support this feature? 2010 only?

Re: how i can unite group of controls and form code to use it in future projects

Patrick Halstead — Thu, 27 Jan 2011 04:36:57 GMT

Have you tried creating an XML Template Part from it? Search this site for XTP and you will be amazed at the possibilities.

how i can unite group of controls and form code to use it in future projects

temp-x — Wed, 26 Jan 2011 08:21:00 GMT

hello everybody)

i have group of control and behind code which proccesed events (buttons and ect..), how i can unite it all as special control to add it in another projects? finaly i want to use it as component when i will add it on a form it would create fields and add program code :)

thanks.