VBA CurDir: what is the use of this? Is there any practical example when you would use CurDir/ChDir etc instead of a simple path?

[Jamualson]

I was wondering what is the use of CurDir, ChDir, etc in practice. Seems to me that using simple paths is always a much more clean way of doing things than curdir etc, which are way too overcomplicated. (ofc it comes from cmd and linux things, but I still don't have an idea why would somebody use this in Excel)

With CurDir / ChDir etc you can lose control. With paths you can not.

Thank you very much for your idea.

 

[Jamualson]

+another thing: you can still use activeworkbook.path, which gives back the folder the file is in, so this is another minus point for CDir and ChDrive functions etc.

Any feedback would be appreciated if I am missing some important point or not Thank you

 

[Toadstool]

Hi Jamualson,

I'm not a VBA programmer but it would seem to me that you don't know where others will use your VBA.
e.g. If my current directory is C:\MrExcel\Toadstool then maybe I want to CurDir, MkDir a Temp directory and then put the results of my execution into there rather than hardcoding a results drive and directory.

 

[Jamualson]

Hi Jamualson,

I'm not a VBA programmer but it would seem to me that you don't know where others will use your VBA.
e.g. If my current directory is C:\MrExcel\Toadstool then maybe I want to CurDir, MkDir a Temp directory and then put the results of my execution into there rather than hardcoding a results drive and directory.

Thank you for the answer. Yes, but this feature can be controlled by activeworkbook.path - according to me in a much more reliable way -, and we still don't loose flexibility. Thx for anybody who could confirm me or make me change my mind.