I'm looking to explore the characteristics of Pure Basic,
and ask for help to the forum to enlighten me on the following:
Since I intend to use the language for business purposes I have found that I can use some databases, but has some ease of reporting?
And for the introduction of multi-line data rows ( Ex. introduction an invoice lines)
Thank you in advance to those who make themselves available to help.
(Obs .: My English is not very correct)
Commercial applications and Pure Basic
- RichAlgeni
- Addict

- Posts: 935
- Joined: Wed Sep 22, 2010 1:50 am
- Location: Bradenton, FL
Re: Commercial applications and Pure Basic
Purebasic can handle a number of database products out there, either native (such as Postgres), or with external libraries (mySql). I personally prefer Postgres. It's free, open source, had great documentation throughout the internet, and is well supported by Purebasic. Also, there is no licensing issues such as with MySql. You could also use the ODBC library inherent in Purebasic to access a database such as Microsoft Sql Server.
For reporting, I have two suggestions: the first is to NEVER use multiple lines per row. When you have a situation like this, create an 'invoice_header' table with the key being the invoice number, containing data such as the invoice date, due date, client reference, terms, etc. Then create an 'invoice_lines' table. Each row in this table will be a separate line in the invoice with its own key, and an external key referencing the 'invoice_header' table. This external key should be 'not null,' and allow duplicates. This leads into the second suggestion: find a good, open source report creator/writer online. Any report creator/writer will handle linked files better than a field separator, which would be required for multiple lines per row.
For reporting, I have two suggestions: the first is to NEVER use multiple lines per row. When you have a situation like this, create an 'invoice_header' table with the key being the invoice number, containing data such as the invoice date, due date, client reference, terms, etc. Then create an 'invoice_lines' table. Each row in this table will be a separate line in the invoice with its own key, and an external key referencing the 'invoice_header' table. This external key should be 'not null,' and allow duplicates. This leads into the second suggestion: find a good, open source report creator/writer online. Any report creator/writer will handle linked files better than a field separator, which would be required for multiple lines per row.
Re: Commercial applications and Pure Basic
It should be noted that the licensing issue only pertains to the distribution model of the MySQL binaries themselves, and not to PureBasic's built-in database libraries that are used to access the MySQL databases.RichAlgeni wrote:...there is no licensing issues such as with MySql.
The only licensing stipulation is that the MySQL binaries should not be included in the same distribution packages as the commercial software that use them, embedded or otherwise. However, distributing them on separate medium free-of-charge, or script-downloading them from within the commercial application, is perfectly legal.
Texas Instruments TI-99/4A Home Computer: the first home computer with a 16bit processor, crammed into an 8bit architecture. Great hardware - Poor design - Wonderful BASIC engine. And it could talk too! Please visit my YouTube Channel 
Re: Commercial applications and Pure Basic
thank you very much for the help.
I will return to this later.
I will return to this later.
