Well I guess you're on IIs right?
This directive can be set for Windows too.
php_value include_path ".:../:./inc":../inc"
Except you use a semi colon instead of a colon to separate paths.
So the question comes down to setting directives, you don't have access to php.ini and IIs doesn't have anything similar to .htaccess (at least as far as I know). This is another reason I like Apache!
You can set the include_path directive at run time too with the ini_set function.
ini_set('include_path', '.;C:/Windows Path/1;F:/www/');
Of course that isn't nearly as useful and if your files are all spread out will be frustrating to implement.
Personally to avoid things like this I tend to chose absolute paths.
if (!isset($_SERVER['DOCUMENT_ROOT']))
{
$_SERVER['DOCUMENT_ROOT'] = ''; // Manually define the path to the www root dir.
}
define('ABSOLUTE_PATH', $_SERVER['DOCUMENT_ROOT']);
include ABSOLUTE_PATH.'/includes/classes/library.class.php';
With this you have but one line to change if moving to a new server or shuffling files to a new directory (considering you have a reusable library and templating system). And even that one line is uneccessary should the $_SERVER['DOCUMENT_ROOT'] variable already be defined for you (don't think IIs provides that variable, Apache does).
You also avoid the circus of relative paths with this approach. Relative paths are fine and dandy till you want to include a script in a sub directory (which contains relative paths) in a script in a different directory, which causes the relative paths to not resolve.
Same thing for any HTML being output. Better to use an absolute path like '/images/file.jpg' as opposed to 'images/file.jpg', the latter won't be found if you decide that you need to include that script in a script in a different directory.
HTH!
Regards,
Rich
--
[
http://www.smilingsouls.net]
Mail_IMAP: A PHP/C-Client/PEAR solution for webmail
Author: Beginning CSS: Cascading Style Sheets For Web Design