PureBasic Forums - English

Hello All PB Community!

Soon i am starting to work on a commercial DB application for a little company.
Before i get started i wanted to get some advices from more experienced programmers whom already written these kinda "Customer Managment" applications

My questions is what features it should have ? what are the rules for making a DB program if it is creating a Backup option or importing Excel files to the DB or exporting reports as PDF file... and so on. (maybe i am missing an important factors)
I would really like to hear your advice and guiding on your point of view of making a skeleton of a generel DB program.

Thank you

Pantcho.

Hi Pantcho my friend, nice to see read you again.

Its very difficult to answer your question as I dont see what your Database should do. Ive done some commercial DBs using access as flatfile whichs works like a charm. For bigger database I would advice you to use a stable database system. e.g. MySQL or something else.

ATM I'm creating a bunch of Database commands like creating reports out of a database etc.

Normaly I use two databases. One wich holds all the basic datas and codes. For static datas I allways use IDs to avoid problems and it makes creating reports and statistics easier. InnerJoins are your friend.

Make your database readable as possible. And if you are using PB to create your frontend dont use Column-numbers, use column names instead.

hm what is importend too!? -think about-
oh Yes... I never delete a database-row. I only make it as beeing deleted. So I avoid the problems of missing datas while browsing old datasets ins the past history.

If I have some more Ideas I will let you know.

Hi Tranquil, good old buddy
Sorry i bouncing this topic again but i have to do this kind of DB and i want suggestions from you or ANYONE that want to help.

1. My DB is an MDB access file.
2. I need to create at least 8 tables = not such a HUGE DB but i assume 400 rows (* 8 tables)
3. Each table has identifier to connect other with the SQL "JOIN" command.
4. For each table i need to create a dialog-window, that:
a. display
b. edit
c. print data

My question is ... how do you handle DB stuff when you need to display them and also to edit them? i toought of making a duplicate hidden gadgets where it dispalys the data and when the user press a button it will go on "edit mode" and unhide duplicated gadgets and hide the display gadgets, then the user will Save/Cancel.
Is this a good method? or there are smarter alternatives?

*edit*:
forgot to mention, how do you print reports ? do you use a library? or use WebGadget?
And if using webgadget - Is printing this method will get all the table fields in the print area?
*edit*

Any other suggestions will be great.
Thank you.

Pantcho,

Rather than creating screens from the tables, you mind find it better to find out how the users will use the application.

Get some user stories walking through some possible scenarios, and then write the application to make those stories go smoothly.

The easiest way to do reports is to generate HTML and show in the browser.

GedB wrote:... The easiest way to do reports is to generate HTML and show in the browser.

This is true, but IMHO it's not as flexible (to work with) as a real gui (if there are different lists at the same time).

Maybe one way is to use several WebGadgets to get the same flexibility (in a custom window not a browser like ie or firefox)

I am talking about the editing part of the DB not the display part.
For the display part i will have a ListIconGadget that display all the wanted fields, for example if they will want to see only name,age,dateofbirth

then the listicongadget will have 3 fields. i am making this dynamic for good use.
The listicongadget i will put in a TAB in PanelGadget and in the second tab i will put the Profile of the DB listicon row with the WHOLE info,i have to do it if they want to edit changes but what is the best way to do so? hidden gadgets as i said before or a new editing window??

I want to know from your experience before i make mistakes and wasting time on GUI design and useless window/gadget event handling code.

Thank you.

Pantcho,

Take a look at how asp.net datagrids work. You probably want to do something like that. (Hidden widget group).

Keep it as simple as possible, but no simpler! (- Einstein?)