INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: using path structure in calculated fields replaces them with "_" - how to avoid?  (Read 257 times)

ShayB

  • World Citizen
  • ***
  • Posts: 103

hi,

while syncing to handheld device,
what should I do in order to force the value of a calculated field (which holds a path structure) to use the backslashes in it and not convert them to a flat directory?

for example:
[someCalculatedField] =   Audio\[genre]\if(isempty([Album]),,[Album]\)

The directories become   Audio_[genre]_if(isempty([Album]),,[Album]\)

(windows OS, MC33)
Logged

zybex

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2966

There doesn't seem to be a way to avoid that.
Why not use the same expression as you have on that field definition, on the Handheld>Audio Path setting?
Logged

ShayB

  • World Citizen
  • ***
  • Posts: 103

There doesn't seem to be a way to avoid that.
Why not use the same expression as you have on that field definition, on the Handheld>Audio Path setting?

Thanks, I can try, however it is a complex expression which I reuse for other uses as well, so, I was hoping to encapsulate it once and reuse it many times.
by the way, copying the whole expression into the 1-liner path argument has an issue of adding the char ";" after each line ending (the expression is written over several lines)

There is a way to do it when doing renames (F6) by using an option button to avoid that. Is it possible to add the same concept for handheld syncs?
Logged
Pages: [1]   Go Up