Tons of File/Directory Manipulation.

[Brandon Smith]

I have read into the FindFirstFile and FindNextFile functions for windows extensively, and read numerous threads on the topic, but can't seem to break it down and figure out how to use it for what I need it to do. I am looking for any sort of help or further guidance so I can get started on this part of my project.

The following is what I need to accomplish:
1. I need to access and create a list of all of the sub-directories within the programs current directory.
2. I need to access and create a list of all of the files within each sub-directory.
3. I need to rename the files within each sub-directory numerically, i.e. 1, 2, 3, 4... etc (optional, but will make life easier).
4. I need to be able to move the files from within the sub-directories to somewhere else.
5. I need to be able to access the names of the files and their locations when they are all finally sorted to be used in writing html code. I.E. somehow pass the paths as a string when using fprintf, etc.

I have no idea where to even begin so ANY guidance would be much appreciated. This is a pretty big project for me to be trying to undertake, which I realize.

Thinks I have already read:
FAQ > Accessing a directory and all the files within it - Cprogramming.com
FindFirstFile function
FindNextFile function
file management in c
Help with renaming multiple files
As well as numerous other threads here on the boards.

[grumpy]

Your reading can't have been nearly as extensive as you claim. Most of the documentation on FindFirstFile() and FindNextFile() - including simple links you gave - give simple code samples of their usage.

Call FindFirstFile() first, then FindNextFile() in a loop, to step through the list of files in a directory, one at a time. If you want a list of filenames, add the filename to a list. Remember to call FindClose() when the loop is done. Bear in mind that second argument (to both FindFirstFile() and FindNextFile()) is the address of a data structure. The filename the functions place in that structure is typically relative to the directory being walked through. To get a fully qualified file name (path and filename, appended) you need to append the filename and an intervening (back)slash to the path name.

If you look up the GetFileAttributes() function, you will find it provides a way to test if a fully qualified filename is for a directory. If you are running through a directory using FindFirstFile()/FindNextFile(), consider what you need to do if you encounter a directory. Recursion provides an obvious method here.

If you want to rename or move files (renaming is often just a move, that just happens to be on the same device) look up win32 API functions like MoveFile() and CopyFile().

I've seen people do all five things you describe, and more, in much less than 50 lines of code. That is not what I call a "big project", by any means. I'm assuming your program doesn't need to handle slightly more advanced things, like symbolic links to files, but information on those are also easy to find if needed.