Janusz

But still, we have another discovered issue (SQL trail issue that you found) to be solved.

   Great to know that you have solve your issue. This forum is great to share our experience and knowledge with each others. Hope you enjoy it.

I tested further after I read your post, and found that I got the issue when I turned on the SQL trail. The issue was gone after I turned of the SQL trail.

Hope this helps.

  I was unable to view your issued. Anyway, if you have any good suggestion, kindly let me know.

Thanks.

  Beware of using SQL Trail.

  I have some issue when using SQL trail for debugging. I have spend quite some time to understand how it work. And finally, I have turn off this features and everything work fine.

The scenario was:

  1) Create a new customer branch
  2) Add Branch Contacts and here it hit an error. (The branch id should be pass to the branch contact when you create a new contact information in branch). When you activate the SQL trail. The branch id doesn't return but it return the wrong id when you execute the sql statement to retrieve the branch id using db_insert_id();

This db_insert_id(); should return the branch id but rather it return the wrong id from 0_sql_trail -> id.

For example: Insert branch return 100;
When you activate the SQL trail, it execute another sql statement to insert the debugging message in 0_sql_trail. and the sql_trail -> id now = 101.
When you execute the db_insert_id(), you expect the returning id is from branch id but instead it return 101.

When I turn off the SQL trail, and re-create the branch and branch contact. It works fine. The returning branch id is correct.

Suggestion: Please change these SQL Trail features to store the message in text file rather then in database. it will help a lot and save time for new developer like me who are trying to change FrontAccounting module. If you have any better idea, please share it with me. Thanks you.

So, as long as the result is 1, I can ignore the error message?

I activated SQL trail option ($sql_trail = 1), and found that some (or maybe all) of error messages are inaccurate.
For instance, I added a new customer. The new customer data was successfully saved. But in the sql_trail table I found these rows:

=================
sql | result |msg

BEGIN | 1 | could not start a transaction

INSERT INTO debtors_master (name, debtor_ref, address, tax_id, dimension_id, dimension2_id, curr_code, credit_status, payment_terms, discount, pymt_discount,credit_limit, sales_type, notes) VALUES ('Dummy Customer', 'Dummy Customer', 'Jakarta', '','0', '0', 'IDR', '1', '2', 0, 0, 1000, '1', '') | 1 | The customer could not be added

COMMIT | 1 | could not commit a transaction
=================

I saw that the new customer data existed in debtors_master table.
So why did the SQL trail tell me that the query was failed?

Was it because the debtors_master table is MyISAM?

Then I tried to do another transaction with InnoDB tables. I added a new item tax type (the item_tax_types table is of InnoDB type). The new data was saved correctly (I think so). But still, I got similar error message in sql_trail table:

=================
BEGIN     1     could not start a transaction
INSERT INTO item_tax_types (name, exempt) VALUES ('No tax','1')     1     could not add item tax type
COMMIT     1     could not commit a transaction
=================

Is there any body can help me to explain this?
Thanks in advance.

Albert