WRITE # and PRINT #

[bartok]

Hi,
I must create some CSV files, but I have noticed that, if for example, I write:

PRINT #1, "hello1"
WRITE #1, "hello2"

hello2 is written on line 1, over hello1. In order to have on line 1 "hello1" and in line 2 "hello 2", I have to use or only PRINT # or only WRITE #.

Is there a way to combine both, or to use WRITE # in a way where is possible to write characters such "?

[bplus]

Fellippe explained pretty well here: https://www.qb64.org/forum/index.php?topic=3986.0

My reply #4 was about using WRITE # only for CSV files that I learned from vid.

[TempodiBasic]

It is an interesting issue I must decide to see last 3 video of Fellippe!

in the while this code seems to have no issue mixing INPUT and WRITE

Code: QB64: [Select]

1. filename$ = "testfile.dat"
2. x = 1: y = 2: z$ = "Three"
3.  
4. Open filename$ For Output As #1 'opens and clears an existing file or creates new empty file
5. Print #1, x
6. Write #1, y
7. Print #1, z$
8.  
9. Close #1
10.  
11. Print "File created with data. Press a key!"
12.  
13. K$ = Input$(1) 'press a key
14.  
15. Open filename$ For Input As #2 'opens a file to read it
16.  
17. Input #2, a, b, c$
18.  
19. Close #2
20.  
21. Print a, b, c$
22. Write a, b, c$
23.  
24. End
25.  

so it is better to see video on files to get the issue instead to wait to fall in it!

[bplus]

Yeah wont see a difference until do this:

Code: QB64: [Select]

1. Open "Test.txt" For Output As #1
2. Print #1, "hello1A", "hello1B"
3. Write #1, "hello2A", "hello2B"
4. Close #1
5.  
6. Open "Test.txt" For Input As #1
7. While Not EOF(1)
8.     Input #1, t$
9.     Print t$
10. Wend
11.  

Here is what Test.txt looks like:

hello1A       hello1B
"hello2A","hello2B"

  [ You are not allowed to view this attachment ]  

[TempodiBasic]

Hi Bplus
as before I have said "better to follow the video and get the issue than fall in the issue while you are building a program".

So I have followed the magnific video  of Fellippe "file part 1" and finding it very interesting I have saved the file codes of the different examples showed by Fellippe.
I post a zip with all these codes into it here because the original thread is locked. Only .BAS.

[bartok]

Fellippe explained pretty well here: https://www.qb64.org/forum/index.php?topic=3986.0

My reply #4 was about using WRITE # only for CSV files that I learned from vid.

I have seen the videos 1 and 2. Very interesting.

Yeah wont see a difference until do this:

Code: QB64: [Select]

1. Open "Test.txt" For Output As #1
2. Print #1, "hello1A", "hello1B"
3. Write #1, "hello2A", "hello2B"
4. Close #1
5.  
6. Open "Test.txt" For Input As #1
7. While Not EOF(1)
8.     Input #1, t$
9.     Print t$
10. Wend
11.  

Here is what Test.txt looks like:
  [ You are not allowed to view this attachment ]

Speaking about CSV files, I found the problem. By your code I have seen that using WRITE #, after using PRINT #, the line used is the following.

In my code, it didn't work, because it was like that:

        PRINT #1, "In Windows settings the index separator character mus be " + CHR$(34) + CHR$(44) + CHR$(34) + "."
        WRITE #1, "BLA BLA BLA"

in this case, "BLA BLA BLA" (IN EXCEL) is not written in the following line, but in the next cell.

The problem is CHR$(44), that is the comma, that in my Windows settings is the index separator. The ame using "," instead of CHR$(44).

So the problem, that is avoidable simpling writing "comma" instead of ",", is how is it possible to write a "," in a CSV file that is visible in Excel as a comma.

[bplus]

I think commas enclosed by parenthesis would be OK, you have to say what Excel does with these:

Code: QB64: [Select]

1. ' this outputs everything in 1 line, does Excel do same?
2. Open "Test.txt" For Output As #1
3. Write #1, "hello1A", "hello1B", "blah, blah, blah"
4. Close #1
5.  
6.  
7. ' this outputs a list, each item on separate line, does Excel do same?
8. 'Open "Test.txt" For Output As #1
9. 'Write #1, "hello1A"
10. 'Write #1, "hello1B"
11. 'Write #1, "blah, blah, blah"
12. 'Close #1
13.  
14.  
15. Open "Test.txt" For Input As #1
16. While Not EOF(1)
17.     Line Input #1, t$
18.     Print t$
19. Wend
20.  

[bartok]

I think commas enclosed by parenthesis would be OK, you have to say what Excel does with these:

Code: QB64: [Select]

1. ' this outputs everything in 1 line, does Excel do same?
2. Open "Test.txt" For Output As #1
3. Write #1, "hello1A", "hello1B", "blah, blah, blah"
4. Close #1
5.  
6.  
7. ' this outputs a list, each item on separate line, does Excel do same?
8. 'Open "Test.txt" For Output As #1
9. 'Write #1, "hello1A"
10. 'Write #1, "hello1B"
11. 'Write #1, "blah, blah, blah"
12. 'Close #1
13.  
14.  
15. Open "Test.txt" For Input As #1
16. While Not EOF(1)
17.     Line Input #1, t$
18.     Print t$
19. Wend
20.  

All you have written works fine. using comma with PRINT #, as I was trying to do, it doesn't work, but with WRITE # it does. With WRITE # it seems that it is also possible to print ", using CHR$(34), so... I think to have get lost in a glass of water!

[bplus]

I think to have get lost in a glass of water!

I don't think you have to but that is an interesting expression. :)

[TempodiBasic]

Hi QB64 coders
here the .BAS written by Fellippe in the video File Part2.


@bartok AND @bplus  here some difference in sentences and proverbs between english and italian languages:

Perdersi in un bicchiere d'acqua
To lose oneself in a glass of water/
To drown in a glass of water
To be easily discouraged.

Read more: https://www.lenntech.com/water-proverbs.htm#ixzz72QP1uj7I

here the links https://www.lenntech.com/water-proverbs.htm
https://hinative.com/en-US/questions/16507733

[bartok]

I don't think you have to but that is an interesting expression. :)

Yes, I also agree that I don't have too:DD