How can we compare the datatypes of array

[Amy222000]

Each column have group of arrays. Example:

PGM DIA

KEY DM
500 122.2
WAIT 0
1000

Now, PGM can have array of string and numeric
DIA can have only string, numeric and numeric once- no array

I want to check now each column contains proper datatype , how can I do so?
I am attaching variant example file for different data types but I am not sure how can I use it properly for my case.

[Johnner]

I'm not sure I fully understand the problem.

Are your source data columns coming out of a tab-delimited file? Is the main problem here one of parsing the source data into an array of steps (or some such) that can be represented using the same datatype? Have you considered the option of simply keeping the data for a given step in the form of an array of strings until the point where you need to use it, and then parsing/interpreting it at the point of consumption?

In general, your approach of using a cluster with a string tag and a variant seems OK, although many LabVIEW programmers might use Flatten to String instead of a variant. Either way, you're eventually going to get to the point where you need to unpackage the data and consume it. But you seem to be OK with that, so I guess I can't see exactly what problem you have.

More information, please,
John

[Amy222000]

I think message is not coming exactly how I am trying to give example so, sending .doc file for the message body.

Message Edited by Amy222000 on 05-04-2005 10:33 AM

You should find all the file that I have been working on in this zip file. Read 2D is making 2d array from spreadsheet. test_machete_andy _ where to split array rearranges data.2D_to_string_Mar_18 have comparison for function name and added data type for each function. I know my files are mess, sorry for that but i am a new user and so much confused with all this. Thanks for your help.

Message Edited by Amy222000 on 05-04-2005 10:41 AM

[Johnner]

Sorry, but I still don't understand the question. You made a good effort to attach your work, but the zipfile still doesn't contain all the subVIs you are using; when I try to open test_match Andy.vi, LabVIEW cannot find Excel Try Opening Again.vi, new_temp.vi, etc.).

If you're not familiar with VI libraries, this is the right time to create one (Save with Options >> Development Distribution). That way, all the necessary subVIs will be included in the resulting .llb file.

That said, I'm afraid I still wouldn't be able to help even if you included all of your work, because the big problem here is clarity. I still don't understand what your main question is. You might want to stick with one VI at a time, getting help at each step, so that you can zero in on specific issues and (ideally) attach simpler VI libraries with just one top-level VI that you're asking about.

Still willing to help if you can clarify things,
John