[TOphotog]

While this might sound trivial to some, I use voicenotes extensively for business and I am having a weird problem with the numbering. I saw a quick CB.com video about voicenotes and noted that the numbering system is supposed to be VN-YYYYMMDD-000x and yet mine is strange. Example:
VN made Nov 3 VN-202203-00001
VN made Nov 19 VN-2041-00009
VN made Nov 20 VN-2042-00001

Does anyone know how I can reset the numbering so it coincides with the actual date? Any help would be greatly appreciated by this otherwise-very-happy PB user. BTW, date and time are set correctly in Options.

[kbz1960]

I have no idea how or if that can be done but for now you could rename them how you want to.

[LimeTripBlog]

Why do you need voice notes, just use free apps like EverNote.
You can rename the file using filebrowser, check out the screen shot.

[TOphotog]

Yes, I know I can rename them. I just want the software to name them properly. I can then match them to my calendar entries.

BTW, LimeTripBlog, it would appear that your files seem to name themselves like mine. Weird? Maybe it was the software upgrade?

[CurtJ]

To the OP:

This is definitely a bug. When the Playbook was first released the file name format from Voice Notes was VN-YYYYMMDD-0000x. Somewhere along the way an OS update changed this.

I opened an incident with RIM to have it changed back to the original format. Hopefully, this will be done in a not too distant future update.

[FF22]

If you grab a file manager, even if you don't rename them, you can look at the creation date and match that to your calendar - I THINK!

[LonelyTylenoL]

To the OP:

This is definitely a bug. When the Playbook was first released the file name format from Voice Notes was VN-YYYYMMDD-0000x. Somewhere along the way an OS update changed this.

I opened an incident with RIM to have it changed back to the original format. Hopefully, this will be done in a not too distant future update.

Beginning Jan 1, 2012, the file naming is back to original format. It is:

VN-YYYYMMDD-0000x


My observations:

VN files created in November and December 2011 were improperly named by the OS.
July and August 2011 VN files were properly named. Don't know about October 2011.

The non-orginal format naming scheme seems to have involved adding up the numbers of the date, e.g.:

VN 2033 is 11/11/11

VN 2045 is 12/22/11


Odd . . .

LT