hello,
i need some help.
does anyone know how to remove "{ }" from the array output from a "collector"?
when saving array output of the collector to file, those {}s are coming along with the data, so
i can't use the saved data with "MS Excel".
thank you in advance.
yoshihiko
hi Stan,
Thank you very much for your reply. I really appreciate that.
yes, you are right, as shown in the attached picture, i'm collecting data from a record.
so, in that case, i should take "plan b", right?
but, one more question, how should i do to transform the record-style data and write to
file whitout brackets? can i do it by choosing an appropriate data format in "To File" block
or by inserting some opertors or functions to the flow?
best regards,
yoshihiko
Hopefully you already saw my reply, but just in case:
Yes- all that's needed is the appropriate transaction in your TO FILE. In this case it sounds like you are writing a record array using default format, which will indeed function but as you found it is structured data in ASCII format. That's to be expected- it is afterall a record, which is structured data.
What you want to do is to write specific FIELDS from your record, as opposed to just your record
For instance if your record is an array and is placed in the variable A then it sounds like what you have now is just WRITE A and of course you get the whole structure of the record along with the field data
whereas what you probably want is something more like WRITE A.length (or whatever the field name is) so that the array A.length is written out, which would be just numeric values with no structure
If you get lost post a more specific example to VRF and you'll get help right away.
regards
Stan
hi Stan,
Again, thanks for your help. But I'm sorry to say, still I couldn't get that.
However, I could manage and got the result that I wanted to. As shown in the attached picture, after sorting the arrayed data in ascending order, unbuilding and writing data one by one to the file, that worked.
But I'm sure you have much better and simpler way to do that. I couldn't understand "WRITE A.length" that you mentioned in you last message. Could you show me exactly where to type "lengh" in? (in "To File" transaction?)
Anyway, I really thank you for your kind and quick relpy.
best regards,
Yoshihiko
In a slightly warped way, it is quite a testimony to VEE that someone can write code without knowing what they are doing and someone else can pick up that code, also without training, and modify it do something else useful! Try that with something like Objective C. Or try taking an 8 year old non-programmer and less than one day of training get them programming in C#.
Anyhow- good to hear that you are up and running. I'll put together a primer on records and get it posted so that others may benefit. In the meantime, you might want to check out chapter 11 in the VEE programming guide over on VEEOS ( http://veeos.org/documents/E2120-90002.pdf ).
regards
Stan
hi Stan,
Thank you very much. I will.
regards,
Yoshihiko
Those brackets are not being added by the collector, but are instead almost certainly part of the data that you are feeding to the collector. Trace the data path back to the source and you'll find where they come from. Or go the other direction: collectors don't write data to a file, so trace the collector output to where your file is being written and then look at the formatting specified in the WRITE transaction(s). Although, if your data is text as I suspect, then formatting later won't help and I'm back to the original suggestion: trace back to where the data is created. If you are collecting text then fix this by collecting numeric data so that you can later write in any format you like. Another possibility is that the data is in the form of a record, in which case the brackets aren't part of the data at all- but are rather an artifact of how the data is displayed or written. In which case "plan b" is the way to go- format the data as you like when it gets written to the file.
Bottom line though- the brackets are not related to the collector, though may or may not be part of the data itself. You need to look elsewhere in your program.
Stan