InfoPath Dev

Hi,

Does anyone know how to use relative addressing in InfoPath?

I want InfoPath to look at other forms in the directory it is inserted into,
without having to re address every external Form that is addressed in a Form.

That is what I mean by relative addressing.
And if there is such a thing, can you please tell me.  Relative addressing was great in EXCEL. But not InfoPath!!!!!!

DOES ANYONE KNOW????? 

I'm not really sure what you mean by "I want InfoPath to look at other forms in the directory it is inserted into,"

If you have Visual Studio, you can publish an InfoPath form as an installable template (.msi).  A user runs the MSI, specifies the installation directory, and then the template can be opened from that location.  If a user creates an XML file using the template, InfoPath will open the XML file using that template the next time the XML file is accessed.

Is that anything like what you are trying to accomplish?

Hi Jimmy,

Firstly for the question you asked.  "look at other forms", 
I should have said other forms that a form can call or connect to. I don't want to have to fully enter the filepath in some of the dialog boxes

such as        "C:\My Documents\InfoPath\VersionD\Formname.xsn".
I'd rather use "..\formname.xsn".  

Is that possible, and if so how? 

Secondly, How do I get to use the .msi?
Is it part of the SDK?
Is it related to publishing a form?  How do I use it?
   NOTE: I don't want to publish and send across the internet.
             The application and forms will not be shareable.

Does the .msi recode the paths I mentioned above?

Is it worth using VisualStudio .NET  development routines?
as referenced in the book
     "MCAD / MCSD Developing and Implementing Windows based Applications
       with Visual C# .NET and Visual Studio .NET".              by Amit Kelani 2002.

It is and old book but mentions forms, and deploying Windows based applications etc. 
But they reference and use code.
It is a book that came out just before the first InfoPath version (2003).
They mention XCOPY and "Solutions Explorer".
Is it worth my while to use some of their ideas to pursue development of a deployable package. 
Like using some of the Visual Studio .NET types of editors, and they are - File System Editor, Registry Editor, File Types Editor, User Interface Editor, Customs Action Editor and Launch Conditions Editor.

I have raised a few questions here hope you can answer them all ??
Thanks ahead if you can.
Ian