reading and writing to a file

[johnblood]

Hi,

I'm doing my best to learn QB64 by writing little apps. One of the things I'm working on is a terminal-based (because I'm still learning) ordering app. Basically, (ha) the customer would be asked for their information (name, address, phone) and then can pick the items that they want.  The app would then total everything up and give them a total.

I'm wondering how I would write their information and order to a file? Preferably a txt or csv file.

Thanks

[SpriggsySpriggs]

Check these wiki links:

https://qb64.org/wiki/OPEN
https://www.qb64.org/wiki/PUT
https://www.qb64.org/wiki/PRINT_(file_statement)
http://www.qb64.org/wiki/PRINT_USING_(file_statement)

[SMcNeill]

Easiest file method to start with is PRINT and INPUT.

OPEN “UserName.txt” FOR OUTPUT AS #1
PRINT #1, “Joe Smoe”
PRINT #1, “123 Not Here LN”
PRINT #1, “Nowhere, NS 98765-4321”
CLOSE

And the above has written your data to a file. 

To read it back, open the file for INPUT and use LINE INPUT #1, variable$ to read that information back into your program.

[bplus]

Yeah, guys but what he really wants is a Database?

Does he want to toy around in Basic building his own (which we luv of course) or does he want to go professional and not reinvent the wheel and get job done right by the thousands who worked through this and built serious and dependable tools?

[SMcNeill]

Yeah, guys but what he really wants is a Database?

Does he want to toy around in Basic building his own (which we luv of course) or does he want to go professional and not reinvent the wheel and get job done right by the thousands who worked through this and built serious and dependable tools?

From this: “I'm doing my best to learn QB64 by writing little apps....”   I’d assume he’d want to start at the very basics of input/output interaction, with fully integrated database support being something which comes later down the line.

[bplus]

@SpriggsySpriggs

Whatever happened to that tut to MySQR err, MySQL ?

Too much? weren't you looking for some project awhile ago?

[johnblood]

Yeah, guys but what he really wants is a Database?

I'm not ready to start working with a database yet. Simply writing to a file is all I want to do now.

From this: “I'm doing my best to learn QB64 by writing little apps....”   I’d assume he’d want to start at the very basics of input/output interaction, with fully integrated database support being something which comes later down the line.

Exactly.

[bplus]

From this: “I'm doing my best to learn QB64 by writing little apps....”   I’d assume he’d want to start at the very basics of input/output interaction, with fully integrated database support being something which comes later down the line.

Well while you tell about first steps, I tell about the road this step will take him down.

[johnblood]

A part of my day job is working with a shopping cart and customer management system. So, it kinda makes sense to learn BASIC my recreating what I use everyday. I don't plan for it to ever be used in real life. Just a fun experiment.

Well while you tell about first steps, I tell about the road this step will take him down.

Sounds good to me.

[AtomicSlaughter]

If you use the write command you can create a basic CSV file and load them back easier

Code: QB64: [Select]

1. start
2.  
3. SUB start
4.     DO
5.         CLS
6.         INPUT "[1]Read or[2] Write >", rw
7.         IF rw = 2 THEN rw = 0: Data_Entry
8.         IF rw = 1 THEN rw = 0: Read_Data
9.     LOOP
10. END SUB
11.  
12. SUB Data_Entry
13.     INPUT "please enter a filename>", filename$
14.     OPEN filename$ FOR APPEND AS #1
15.     INPUT "name >", n$
16.     INPUT "address >", a$
17.     INPUT "Tel. No. >", t$
18.     WRITE #1, n$, a$, t$
19.     CLOSE #1
20.  
21. END SUB
22.  
23. SUB Read_Data
24.     INPUT "Enter a filename >", filename$
25.     INPUT "Enter a name to search for >", search$
26.     OPEN filename$ FOR INPUT AS #1
27.     CLS
28.     DO
29.         INPUT #1, n$, a$, t$
30.         IF n$ = search$ THEN
31.  
32.             PRINT n$, a$, t$
33.         END IF
34.     LOOP UNTIL EOF(1)
35.     PRINT: PRINT: PRINT "Press any key to continue"
36.     SLEEP
37.     CLOSE #1
38. END SUB
39.  
40.  
41.  

[SpriggsySpriggs]

@SpriggsySpriggs

Whatever happened to that tut to MySQR err, MySQL ?

Too much? weren't you looking for some project awhile ago?

@bplus I'm very busy these days. I still go back to my MySQL code and make sure it looks decent, though. I want to go back through it again since the Wiki code (where most of it came from) looks sloppy. That, and I want to bring it to v1.5 DIM syntax as well as making sure it is OPTION _EXPLICIT compliant. Once that is done then I'll do a tutorial.... When I have time enough to sit down and do it. But, since johnblood didn't ask about doing a database and is a beginner, I'm not going to suggest that he looks into MySQL or INI manager. It's far better for him to get the understandings of I/O first.

[bplus]

@bplus I'm very busy these days. I still go back to my MySQL code and make sure it looks decent, though. I want to go back through it again since the Wiki code (where most of it came from) looks sloppy. That, and I want to bring it to v1.5 DIM syntax as well as making sure it is OPTION _EXPLICIT compliant. Once that is done then I'll do a tutorial.... When I have time enough to sit down and do it. But, since johnblood didn't ask about doing a database and is a beginner, I'm not going to suggest that he looks into MySQL or INI manager. It's far better for him to get the understandings of I/O first.

Glad to see you are busy, the devil will have to look somewhere else ;-))

Just want to warn johnblood, the Basic way is all consuming if you have wife and kids and professional career get out now before you take those first steps... they will show you a power that is very seductive...

just saying ;-))

[bplus]

A part of my day job is working with a shopping cart and customer management system. So, it kinda makes sense to learn BASIC my recreating what I use everyday. I don't plan for it to ever be used in real life. Just a fun experiment.

Sounds good to me.

Yeah, I know this story, I lived it. That's what we say, just a little fun is all...  ;-))

Next thing you know you are burning the candle from both ends...

[AtomicSlaughter]

This is a slightly more refined version of my previous post with error reporting and partial name search, that prints the output of the seach to the screen.

Code: QB64: [Select]

1. ON ERROR GOTO ErrorLevel
2.  
3. start
4.  
5. ErrorLevel:
6. PRINT "File not found"
7. SLEEP 2
8. start
9.  
10. SUB start
11.     DO
12.         CLS
13.         INPUT "[1]Read or[2] Write >", rw
14.         IF rw = 2 THEN rw = 0: Data_Entry
15.         IF rw = 1 THEN rw = 0: Read_Data
16.     LOOP
17. END SUB
18.  
19. SUB Data_Entry 'Asks for a filename for data to be input to
20.     INPUT "please enter a filename>", filename$
21.     OPEN filename$ FOR APPEND AS #1
22.     INPUT "name >", n$
23.     INPUT "address >", a$
24.     INPUT "Tel. No. >", t$
25.     WRITE #1, n$, a$, t$
26.     CLOSE #1
27.  
28. END SUB
29.  
30. SUB Read_Data ' Aks for filename to open and name search paramerters
31.     INPUT "Enter a filename >", filename$
32.     OPEN filename$ FOR INPUT AS #1
33.     INPUT "Enter a name to search for >", search$
34.     CLS
35.     DO
36.         INPUT #1, n$, a$, t$
37.         IF INSTR(n$, search$) THEN PRINT n$, a$, t$ ' this line seaches for any instance of search$ in the n$ variable
38.     LOOP UNTIL EOF(1)
39.     PRINT: PRINT: PRINT "Press any key to continue"
40.     SLEEP 5
41.     CLOSE #1
42. END SUB
43.  

[191Brian]

Hi

I would also suggest looking at  the open as random option with fixed length user defined types you can build simple database functions that way.  I am planning on using  that for storing game assets.

Brian....