Razzak, Thanks for this timely information. I know that file management has changed over the years, particularly due to Windows changing.
In the past, we used to be able to have "\\" before the filename which told the OS that this file was located in a sub-directory. Jan -----Original Message----- From: "A. Razzak Memon" <[email protected]> To: [email protected] Date: Thu, 10 May 2018 11:54:41 -0400 Subject: [RBASE-L] - Tip of the Day: Managing Folders and File Names Thursday, May 10, 2018 Tip of the Day: Managing Folders and File Names Product.......: R:BASE X and R:BASE X Enterprise (Version 10) Build.........: 10.0.3.20320 or higher Section.......: Managing Folders and Files Keywords......: COPY,CURRDIR,CURRDRV,DBPATH,DELETE,DIR,ERASE,LAUNCH,MKDIR,RENAME When designing, developing, and deploying R:BASE Document Management System on Cloud, how you organize and name your files will have a big impact on your ability to find those files later and to understand what they contain. Consider the obvious when searching, indexing, displaying, and managing folders and files: 01. Set up a clear directory structure that includes information like the project title, a date, and some type of unique identifier. 02. Be consistent and descriptive in naming and organizing folders and files. 03. Don't make file names too long; longer names do not work well when exceeds 260 characters. In the Windows API, the maximum length for a path is MAX_PATH, which is defined as 260 characters. A local path is structured in the following order: drive letter, colon, backslash, namecomponents separated by backslashes, and a terminating null character. The recent most Windows 10 preview is enabling users to change the 260 characters limit. Enabling NTFS long paths allows manifested win32 applications and Windows Store applications to access paths beyond the normal 260 char limit per node. But, why in the world would you name your folder or filename that big? 04. Avoid special characters when naming folders and files. Special characters such as ~ ! @ # $ % ^ & * ( ) ` ; < > ? , [ ] { } ' " and | should be avoided. 05. A good format for dates is YYYYMMDD (or YYMMDD). This makes sure all your files stay in chronological order, even over many years. 06. For sequential numbering, use leading zeros to ensure files sort properly. For example, use "0001, 0002…1001, etc" instead of "1, 2…1001, etc." 07. Do not use spaces, instead use underscores (file_name), dashes (file-- ].name), no separation (filename), or camel case (FileName). Very Best R:egards, Razzak. http://www.rbase.com [http://www.rbase.com/] http://www.facebook.com/rbase/ [http://www.facebook.com/rbase/] -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php [http://www.rbase.com/support/usersgroup_guidelines.php] --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] [mailto:rbase-l%2Bunsubscribe%40googlegroups.com]. For more options, visit https://groups.google.com/d/optout [https://groups.google.com/d/optout]. -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
