Hello...
In the A5V8 documentation, I find the following:
"Table and Field Names
Alpha Five recommends that table names, field names, and paths to your files start with a letter (A-Z or a-z) and be composed of letters, numbers (0-9), and underscore (_) characters."
I am now in the process of "converting" all my FMpro databases to A5V8. Because of one client's requirements to save a copy of their table's data at a particular point, I have been in the habit of naming tables beginning with the date in numerals, i.e., "20080202tablename". From the above info, this might cause problems, although I cannot determine why this naming format would do so. I always put the date first because it sorts the tables by date within a folder.
Having thought about table naming since yesterday afternoon, I have come up with the following solution if the above naming convention might cause problems for me:
Given:
1. The 2000 series of years will be around longer than I will.
2. The first 26 years of the 2000 series of years will be around longer
than my business will, and possibly, longer than I will.
New date convention:
1st character: A-Z, beginning with 2001=A.
Therefore 2008=H, 2009=I, ..., 2026=Z
2nd character: 1=Jan, 2=Feb, ..., 9=Sep, A=Oct, B=Nov, C=Dec
3rd and 4th characters: 01=1, 02=2, .... 30=30, 31=31 (day of the month)
Actually, I like the above as the date can be specified in 4 characters.
It looks like I have answered my own question; but, if I have missed something, please let me know.
Thanks,
Steve
In the A5V8 documentation, I find the following:
"Table and Field Names
Alpha Five recommends that table names, field names, and paths to your files start with a letter (A-Z or a-z) and be composed of letters, numbers (0-9), and underscore (_) characters."
I am now in the process of "converting" all my FMpro databases to A5V8. Because of one client's requirements to save a copy of their table's data at a particular point, I have been in the habit of naming tables beginning with the date in numerals, i.e., "20080202tablename". From the above info, this might cause problems, although I cannot determine why this naming format would do so. I always put the date first because it sorts the tables by date within a folder.
Having thought about table naming since yesterday afternoon, I have come up with the following solution if the above naming convention might cause problems for me:
Given:
1. The 2000 series of years will be around longer than I will.
2. The first 26 years of the 2000 series of years will be around longer
than my business will, and possibly, longer than I will.
New date convention:
1st character: A-Z, beginning with 2001=A.
Therefore 2008=H, 2009=I, ..., 2026=Z
2nd character: 1=Jan, 2=Feb, ..., 9=Sep, A=Oct, B=Nov, C=Dec
3rd and 4th characters: 01=1, 02=2, .... 30=30, 31=31 (day of the month)
Actually, I like the above as the date can be specified in 4 characters.
It looks like I have answered my own question; but, if I have missed something, please let me know.
Thanks,
Steve
Comment