There's no problem with a FILE name beginning with a digit, it's if you're using it as an ALIAS name that will cause you trouble. Aliases can't begin with a digit.

>Then I still have more than one year to fix it, so I should have no problems,
>
>>Not exactly luck:) Now for a long time 2nd character is 1 and 3rd is character (started from A and now at M). I'm not sure on exact date no but from Jan 23rd,2007 I think it'd be _20...
>>Cetin
>>
>>>I have not had any problems with the function Substr(Sys(2015),3) the last 15 years, but I see that I may have been lucky. :-)
>>>
>>>>BTW I assumed there is a need for 8.3 and a filename wouldn't start with a digit. I don't know where it's needed (was usefull in DOS days).
>>>>PS: If you need a unique filename on a shared folder and 8.3 is not a problem then GUID is a better alternative.
>>>>Cetin
>>>>
>>>>>Hehe.. I know. I had lived big troubles with that... The best way combine it with a unique number like user number which I use. I lock a record when a user enter the network and my temporary names begins with it's number..
>>>>>
>>>>>>Metin,
>>>>>>IMHO substr(sys(2015),3) is not safe either (even if not shared) because it's time dependant and from 2007 3rd character would be a digit. What I used was something like this instead:
>>>>>>
>>>>>>stuff(sys(2015),9,0,'.')
>>>>>>