Search options (Page 97 of 200)

Look at the various themes, also those in the repository, to see how the menu presentations are done. You can access the repository frm the setup tab.

Joe

Do you want me to prepare a COA script for es_EC, from this?

I guess the class_id field in the chart_types is wrong, but I can fix this.

Joe

This is ok, Apmuthu. Please continue delving into this formatting. As this can always be implementied during a minor release, we are not in a hurry.

Joe

If you use Customer Transactions Inquiry, and select a customer, you will see his total balance together with an aged balance.

You can get the same result by running an aged customer analysis in the reports. And you can selext a summary only report.

/Joe

No, I don't think there is an extension that can do that at present.

/Joe

This has been implemented, though has the global variable, $hide_inactive_menu_items, has been placed in config.php, with the backwards compatible value of 0.

HG repository updated.

Joe

Some countries has an alternative way of summation. F.i. Tax authorities.

I will ask Janusz to look at this.

Joe

Thank you very much.

Joe

This is not a bug. Please uncheck the 'search item list' in company setup, setup tab.

Joe

Hello again.
This error has now been localized. The 0_sys_types data was missing in the COA.

With phpMyAdmin, please copy and paste the following into the sql box in phpMyAdmin and run it.

If you have another table prefix than 0_, please replace this before running.

INSERT INTO `0_sys_types` VALUES(0, 17, '1');
INSERT INTO `0_sys_types` VALUES(1, 7, '1');
INSERT INTO `0_sys_types` VALUES(2, 4, '1');
INSERT INTO `0_sys_types` VALUES(4, 3, '1');
INSERT INTO `0_sys_types` VALUES(10, 16, '1');
INSERT INTO `0_sys_types` VALUES(11, 2, '1');
INSERT INTO `0_sys_types` VALUES(12, 6, '1');
INSERT INTO `0_sys_types` VALUES(13, 1, '1');
INSERT INTO `0_sys_types` VALUES(16, 2, '1');
INSERT INTO `0_sys_types` VALUES(17, 2, '1');
INSERT INTO `0_sys_types` VALUES(18, 1, '1');
INSERT INTO `0_sys_types` VALUES(20, 6, '1');
INSERT INTO `0_sys_types` VALUES(21, 1, '1');
INSERT INTO `0_sys_types` VALUES(22, 3, '1');
INSERT INTO `0_sys_types` VALUES(25, 1, '1');
INSERT INTO `0_sys_types` VALUES(26, 1, '1');
INSERT INTO `0_sys_types` VALUES(28, 1, '1');
INSERT INTO `0_sys_types` VALUES(29, 1, '1');
INSERT INTO `0_sys_types` VALUES(30, 0, '1');
INSERT INTO `0_sys_types` VALUES(32, 0, '1');
INSERT INTO `0_sys_types` VALUES(35, 1, '1');
INSERT INTO `0_sys_types` VALUES(40, 1, '1');

The repository will be replaced with an updated sql script.
Joe

No, the database structure is different. You will have to change when there is a fiscal year end.

/Joe