🚀 go-pugleaf

"Marc" <bukwheat_NS@axess.com> wrote in message
news:4266bf60@newsgroups.borland.com...

> I am having an issue with retrieving the directory from
> where my application is started from, let me explain...

That is because you are making assumptions that you should not be making.

> GetModuleFileName and GetCurrentDirectory aren't cutting it for
> me.

GetModuleFileName() works fine, you just have to strip off the FileName
portion after calling it.  The TApplication::ExeName property uses
GetModuleFileName().  You can use the VCL's ExtractFilePath() function to
remove the filename from the returned value:

    AnsiString folder = ExtractFilePath(Application->ExeName);

Or, if you don't want to use the VCL, then just place a '\0' character after
the last '\\' character in the string buffer that you pass to
GetModuleFileName():

    char folder[MAX_PATH+1] = {0};

    DWORD dwCount = GetModuleFileName(NULL, folder, MAX_PATH);
    for(DWORD dw = dwCount; dw > 0; --dw)
    {
        if( folder[dw-1] == '\\' )
        {
            folder[dw] = '\0';
            break;
    }

As for GetCurrentDirectory(), that returns the calling process's current
working directory, which can (and usually does) change dynamically (even
multiple times) during the process's lifetime.  You should not rely on the
current working directory at all to determine the folder the application is
executed from.  You cannot even rely on it as the first call in WinMain(),
as the current working directory can be set to a different folder by a
shortcut that is launching the application, before WinMain() is even called.


Gambit