<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Code</title><link>https://www.infopathdev.com:443/forums/45.aspx</link><description /><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Re: Script Utility File?</title><link>https://www.infopathdev.com:443/forums/thread/13497.aspx</link><pubDate>Wed, 24 Aug 2005 06:14:17 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:13497</guid><dc:creator>Patrick Halstead</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/13497.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&amp;PostID=13497</wfw:commentRss><description>The other option is to encapsulate the functions in a web service that you call.&lt;br /&gt;&lt;br /&gt;Patrick Halstead [InfoPath MVP]&lt;br /&gt;InfoPathDev</description></item><item><title>Re: Script Utility File?</title><link>https://www.infopathdev.com:443/forums/thread/13496.aspx</link><pubDate>Wed, 24 Aug 2005 06:13:38 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:13496</guid><dc:creator>Patrick Halstead</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/13496.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&amp;PostID=13496</wfw:commentRss><description>No, unfortunately, you will need to add the same vbs file to all of your solutions. You can convert to a VB.NET assembly that you include which is slightly better, but there is not a good way to share code today.&lt;br /&gt;&lt;br /&gt;Patrick Halstead [InfoPath MVP]&lt;br /&gt;InfoPathDev</description></item><item><title>Script Utility File?</title><link>https://www.infopathdev.com:443/forums/thread/12535.aspx</link><pubDate>Tue, 23 Aug 2005 14:44:24 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:12535</guid><dc:creator>vt_asparagus</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/12535.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=45&amp;PostID=12535</wfw:commentRss><description>I am coding an InfoPath form that is using VBScript and I wanted to create a general set of utility methods that I can re-use across InfoPath forms.  I am trying to build a framework for which my client can continue to build new InfoPath forms upon.  Is there a way I can reference another vbs file, like utilities.vbs, if I were to add it as a resources of the InfoPath form?&lt;br /&gt;&lt;br /&gt;If I could use .NET managed code I would create a code library and include it into the VS InfoPath Solution, but various client requirements I am not using .NET managed code.&lt;br /&gt;&lt;br /&gt;Thanks...&lt;br /&gt;</description></item></channel></rss>