forum.vdsworld.com

moke · Contributor Joined: 02 Jan 2002 Posts: 162

I think we have 2 issues here.

1. Does the parse command removal of spaces constitute a bug?
2. Is there a standard when creating CSV's? And does it include spaces.

I already stated my opinion for #1

As for number 2; After further testing with Access and Excel here's what I found:

Access DOES include quotes when exporting to CSV but only on fields
with a text property. All other fields export without quotes.

Excel DOES NOT include quotes regardless of cell formatting.

I think we can safely conclude that there is no REAL standard (although
there must be a CSV standards committee somewhere with a different
opinion). I must also admit that using quotes on text fields is probably a
good practice to use and I will be changing my code and repenting the
errors of my ways.

Amen & Alleluia Smile

moke

Mac · Posted: Fri Dec 13, 2002 9:05 pm Post subject:

Tommy · Posted: Fri Dec 13, 2002 10:26 pm Post subject:

You really can't count on the parsed fields to be surrounded by quotes, that quite defeats
the purpose of parse (parse splits based on one character (eg. |), not three characters ("|")).
Like Prakash already mentioned, PARSE was never specifically meant for parsing CSV files.
I think the main reason for parse is parsing field separated values, such as the values
returned by @DLGPOS(). Never I've seen VDS's field separated values to be surrounded by
@CHR(34). So I still think it's a bug.

Mac · Posted: Fri Dec 13, 2002 10:32 pm Post subject:

Well, without quotes, the field separator character can
never be included as text. Otherwise it will parse there.

And hopefully I made clear the reason for @chr(34) instead
of standard quotes... Wink

Cheers, Mac Smile

SnarlingSheep · Posted: Sat Dec 14, 2002 6:24 am Post subject:

In just about any other language you would have to have quotes around a string. These quotes wouldn't really be passed to the commands or displayed when used in static text elements, something like @CHR(34) would have to be used.
Using DIALOG SET,Text1,"Test" doesn't show the quotes around Test..why should PARSE be any different really?
We are talking about PARSE removing spaces though..it doesn't seem like it should do that.
I agree with you for the most part Mac, but the bottom line is PARSE removes spaces you are trying to preserve. I'm a firm believer in not having to "work around" things in something you pay for.
Sorry to gang up on ya but I figured I'd speak my 2 cents..now I'm broke so I'll be off Wink

Mac · Posted: Sat Dec 14, 2002 6:39 am Post subject:

Well, PARSE only removes spaces in the same manner
as assigning any other value to a variable - without
quotes, leading and trailing spaces are omitted. Confused

LOL, being clearly outvoted however, I surrender. Razz

I'll move this to the Bug Reports forum. Wink

Cheers, Mac Smile

cnodnarb · Posted: Sat Dec 14, 2002 4:06 pm Post subject:

Mac the Mammoth falls under the weight of the pack of sabre toothed VDS users and a snarling sheep Laughing

NodNarb

(Sorry, been having to watch "Ice Age" with my kids too much I guess)

PGWARE · **Web Host** Joined: 29 Dec 2001 Posts: 1566

[post overwritten on accident]

Garrett · Posted: Sat Dec 14, 2002 7:47 pm Post subject:

Garrett · Posted: Sat Dec 14, 2002 8:23 pm Post subject:

Ah gees!!!! How did I end up writing over PK's post????

-Garrett

Garrett · Posted: Sat Dec 14, 2002 8:24 pm Post subject:

Mac · Posted: Sat Dec 14, 2002 10:12 pm Post subject:

Show 'em on separate lines and it makes more sense
Garrett. Each parsed item is still trimmed because it
doesn't see the quotes... Wink

__________________________________________________________________________________________________________________________

Tommy · Posted: Sat Dec 14, 2002 10:14 pm Post subject:

What I think is there's no need for parse to see the quotes at all, as long as it is able to
"see" the separator character.

Mac · Posted: Sat Dec 14, 2002 10:32 pm Post subject:

Well, PARSE only does two things:

1. Captures the portion of the string between two separators.
2. Assigns that portion to a variable (in the same way other
values are assigned to vars).

Apparently (most) everyone thinks it should assign values in
a different manner than usual. I just haven't figured out why... Confused

Cheers, Mac Smile

Skit3000 · Posted: Sat Dec 14, 2002 10:38 pm Post subject:

Here we go again.... Confused