What kind of image files are referred to in the Path to Image Files setting?  Is it specifically for images that would be used, for example, as labels for an element?  If I want to use @AsynchShell() to launch images with my default image viewer, is this where they should reside?  Would I still need to tell @AsynchShell() the complete path to the image or would it "just look there"?

I'll have some followup questions depending on what I learn from the above.  Thanks in advance.

Thank you.  A couple of followup questions:

* What images are used in the Image Path folder?  (I'll be looking at the Gem database for clues, but I thought I'd ask as well.)

*  If my working folder is F:\Sesame\Miara and I want to use @AsynchShell() with a relative path to elsewhere on the F: drive (say F:\Images, for example), is that possible?  Or is "relative pathing" just tunneling downward?  Currently I have this code working:

// Launches the image whose filename is stored in Image_1

Var vLaunchImage as Int
Var vFullImagePath as String

IF NOT @MODE() = 2     // Check to make sure you're not in the Retrieve Spec
THEN
{
vFullImagePath = (sImageDir + Image_1)
IF FileExists(vFullImagePath)
THEN
	{
	vLaunchImage = @AsynchShell(vFullImagePath)
	}
ELSE
	{
	@MsgBox("Looking for " + vFullImagePath, "but unable to find this file on disk.", "Is the file name correct?")
	}
}
ELSE
	{
	@MsgBox("This button only works in ADD or UPDATE mode", "", "")
	} 

sImageDir is a global static declared in global programming.  It is currently initialized as "F:\Images\".

I would like to use an #include statement to initialize this static (I asked about initializing in an #include in another thread) and relative mapping to make this variable drive independent.  I'm hoping to make all my code drive independent, but I also have some other hard coding elsewhere in my code, namely @Insert() statements that point another global static, sInsertDir to "F:\Sesame\Miara\Inserts".

Thanks again for your help Erika.

Quote:

After some testing I've found that I cannot get this to work without pointing to the F: drive directly, because each workstation has a Start In directory of C:\Sesame.  They work fine if Images is placed on the C: drive.

I'm going to try the #Include route of initializing the Images and Inserts directories.  My main objective is to get the my applications to run on both the network and my laptop, so I can work on it at home.  With the initialization in an #Include file I'll just have to change the pointer in one place rather than throughout my code.  Thanks again for your help.

You could also make two (or more) paths with the variables. 
One path if on the network, another path if using local. 

You could also write some sync code to copy/send files between server and laptop. 

These would be part of Application program to run when app is opened.

Steve,

Is this for image fields or static images/labels?

I'm confused. You have two machines. One is accessing the db as a client. The other is using a second copy of the database as a standalone. Is that right?

Why not just change the image path in the second copy to wherever it need to be?

If the images are always on the same drive as your working directory, changing the Image Path to \photos should do it.

Scott,

In 1.1.5, which is what Steve is running, there is no command to set the Image Path of an Application in code.

-Ray