help with my app (Page 1 of 2)

Please show a screenshot where it is happening (I did not find the "Invoice" and "Order" tables). If this is a new feature, then to create a new record based on records in another table, you will need a script with an SQL query. And an explanation of where in the interface you want to add this and which tables to use.

picture 2

Hello Igor, Konstantin,
Although you have created relationships in your Data Schema between the tables Racuni / Nalozi and Racuni / Kupci, you are not actually populating values for these relationships on FormNoviRacun.
Depending on your process flow / logic, MVD normally populates these relationships for you (I think Kupci > Nalozi > Racuni would be the expected process flow).  But because your processing logic is not like this, you need to populate values for the relationships yourself by using a small script (see the attachment).
If you use a utility like SQLiteStudio, you would be able to see where various relationships were not being populated.  Alternatively (and just while you are developing your application), you could create a form with tablegrids that show all the fields in every table;  this would also show you where the problems could be. 
On FormNoviRacun, I have added Combobox1 and Combobox2 and these are filled with relevant IDs to the Kupci and Nalozi tables;  the relevant columns on FormRacuni should now be populated and showing in the tablegrid.  There may well be other parts of your project where you are having similar issues.

As mentioned in an earlier post, I would suggest you review the whole processing logic of your project as the flow from form to form seems (at least to me) to be overly complicated and disjointed.  This, in turn, will likely lead to more problems as you further develop your project.
Regards,
Derek.

Hi
I am unable to replicate your error.
You need to attach the latest version of your project and explain the exact actions you take up to the point that you get the error.
Also, was it working before and you changed something or has it always given this error.
The more information you can give, the better any help that you receive will be - otherwise it's not much more that guessing.
Derek.

Hi Igor,
The error message is because you have not created a relationship between the 'customer' and 'invoice' tables.
You also need to populate 'FormUnosNovogNaloga.ComboBox1' (line 11 in the script).
This will fix the error that you are getting.
However, there are a lot of other things that are not correct with your project.
As I understand it, your project should, at its most basic
1. add / edit / delete customers
2. add / edit / delete an order for a customer;  this order can have one or more order line
3. add / edit / delete an invoice for one or more order lines that have been delivered to a customer.
As I have mentioned before in earlier posts, until you have this basic functionality working correctly, you should forget about features like coloring grid lines, product images, messages, database backups etc etc;  they can all be added later.
I would also strongly suggest you rewrite - at the very least - FormUnosNovogNaloga and use two separate forms instead (one for orders and one for invoices).
Derek.

Hi Igor,
Have a look at the attachment which, I believe, does the basics of what you need your application to do.  As mentioned earlier, if this is working, then you can add extra features later on.
The example allows
1.  clients can have multiple orders
2.  clients can have multiple invoices
3.  orders / invoices can have multiple order / invoice lines
4.  orders / invoices can initially be created with no lines if that is a requirement
5.  order lines can be partially invoiced
6.  order lines from different orders can appear on the same invoice
If your requirement was only for one order line = one invoice line, the data schema would be more straightforward but I don't know if that's the case.
Regards,
Derek.

Hi Derek,
i cannot delete order, can you try it if it works for you?
Thank you

Hi,
i have one more question, how to make invoice from order?do you have some example?
in your example when i go make invoice i have to do double job, first i have to make order then again i have to make invoice.
it will be easier if i have order to make invoice from that order instead of making invoice from start.

thank you

yup,1 order for 1 invoice.
i must make order first so i can make invoice to customer.
All lines from order go to invoice

thank you

Thank you Derek,
ill go try it

Hi Igor,
10,000 records is not too many (although the PC you run it on will obviously be a factor).
You have previously stated that each order will produce an invoice (one for one);  therefore if you have separate tables for orders and invoices, then you will ultimately have 2 tables, each with 10,000 records which has to be less efficient than holding all your transactions in a single table with 10,000 records.
Obviously you will be adding more tables as you develop your application further but these will be for related data rather than to hold actual transactions.
What can affect the performance is using a lot of calculated fields (very useful depending on the requirement but will probably slow your application down). 
So I would look to replace calculated fields where possible (see attachment which is a re-working of an earlier example with the calculated fields removed).
Regards,
Derek.

Hi Igor,
This is the correct behaviour.
If you try to delete a record that is being used elsewhere, it will compromise the integrity of the database and created ''orphan'' records.
And if you select ''cascade/delete'', then the database will attempt to remove all the records where the record you are trying to delete is being used after which it can perform the deletion.
Referring to your project, I wonder if what you are trying to do is prevent records in the 'services' table being used once the 'pricedate' has expired?  If this is the case, there are other ways to achieve this.
Have a look at the attachment for a couple of options - I have simply added a 'flag' to indicate when a service/item is no longer current and then added a filter to various comboboxes to prevent that record from being used in the future (I also set the price in the 'services' table to 0.00).  Doing it this way means that you can still re-create old orders, old invoices etc that refer to services/items that have expired in the meantime.
Another way (not in the attachment) would be to validate the selection (using a script) and display appropriate error messages (but I think it's better to try and prevent it from happening in the first place).
Regards,
Derek.