Using PHP, ajax and MySql for QMS

[zancky]

Hi everybody,
I'm trying to write down all my QMS in php, ajax and MySql.
Up to now all stuff about incoming material, tracking material, gauges and instruments management and suppliers rating are covered.
I'm currently working on PAPP isuues.
Did anybody do something similar or would like to share experiences?

thanks

[BradM]

Hello, Zancky! Some questions for you....

1. Why are you using so many different applications? Are you not interested in finding one?

2. As far as gauges and the like.... is your application currently covering your need? I have found that dedicated programs for calibration/asset management take care of many of the issues that I am interested in.

As far as your comments requested... are you looking for people to comment on your particular applications, or are you wondering how others have handled the same process requirements as you?

[zancky]

hi Brad,
even if I'm not a programmer, I'm trying to write by myself my applications.
I have taken the choice to write a program that everybody into the plant can work with (multiusers and intranet based).
MySQL is the database, the user opens Internet Explorer or Firefox, type the address of my computer and he should find whatever he need. The web pages and the script have been written by me in php and ajax (more or less like this forum, I suppose). This gives me a lot of flexibility, everything is free of charge and I'm studying something new.

As I have found very competent people here, I would like to compare solutions, strategies, tricks with someone else involved in writing program. No problem to give all the software I have written, I'm for open source!. Doing everything myself I made sometime mistakes that take a lot of time to be solved expecially if they are related to program architecture therefore if someone can help me it would be very appreciated

thanks

[alex_bell]

Doing all this yourself is going to be HARD.

I write some code, mainly SQL, VB.net and C#, for a few applications that are used at my company but they're adding functionality rather than developing a system from scratch.

For what you have described you need to start of with requirements capture. Once you have requirements for each part of your application you then need to do map out some high designs on how things are going to work, which function are going to do what etc. Then you need to write the stuff and then test it.

This is an extremeley superficial look at what you are going to do.

Even the database alone is hugely complex, do you understand about normal forms for databases? If the fundamental design for you DB isn't correct then your going to be in for a rough time as it will perform poorly, use excessive space and you could end up conflicting data.

I would aim a little less high to begin with. Your choice of technologies are good so pick a small thing to begin with and see how that goes and then start expanding.

I will iterate this once again though. A good database design is essential to start with. It's a lot easier to rewrite bits of code than it is to change your database structure.

[zancky]

hi Alex,
thanks for Your answer.
Well I have started 4 years ago. For one year I have studied php and mysql. More or less the current system consists now of about 280 scripts. I have choosen a modular approach so I add a new functionality every 2 months. During the development I started to study ajax and a little of jave updating everytime the system.
About normal form for DB. I know it, but for some special tasks I preferred not to follow the rule and after 2 year, I can cornfirm it was the right choice.
The flexibility of the system for me it is very important. With my program QC generate a lot of reports and forms, therefore if the QMS changes for any reason I can update reports and forms. Not a long time ago design department changed completely incoming material specifications, I have to update db structure, filling forms and reports (two weeks working only on overtime). I don't think that it would be possible with a commercial one.

[CliffK]

In Reply to Parent Post by BradM

1. Why are you using so many different applications? Are you not interested in finding one?

What he's describing is an application development stack.
MySQL is the data repository.
PHP is a programming language. PHP scripts gather data from end users and store it in the repository or search the repository for data and present it to end users.
Ajax is a programming technique using javascript.

This is similar to the stack that runs this site. Look for the software logos at the bottom of this very page.

[CliffK]

In Reply to Parent Post by zancky

Hi everybody,
I'm trying to write down all my QMS in php, ajax and MySql.
Up to now all stuff about incoming material, tracking material, gauges and instruments management and suppliers rating are covered.
I'm currently working on PAPP isuues.
Did anybody do something similar or would like to share experiences?

thanks

In-house developed software is the way to go.

Never used javascript myself, but the php/MySQL combination is excellent stuff.

[goldstar]

I am interested in PHP, at present I'm busy in doing different work, hope after finishing the work I will plan to write about PHP very soon.