Search options (Page 158 of 246)

Generally there are not many changes in databases between these versions. If you have extensions installed then it may need more attention. Which chart of accounts are you using?

The extensions are in my unofficial github repo.

The company folder will have to be writeable anyway.

Please post each issue in separate posts.

Study the existing reporting/repXXX.php file to make your own alignments - see attachment for example.

http://www.w3schools.com/tags/att_meta_http_equiv.asp
http://www.metatags.info/meta_http_equiv_refresh

After Adding a New GL Account, what has been entered in the database is made available for further edit and to verify that it is correct. That is why there is no auto redirection to "New account". You can always program another button for it.

If you want to enter another New GL Account, then choose New account in the top drop down select box as in the attachment.

@sorna: Please post each new issue as a new post in the relevant forum topic. When you get a working solution, please explain it here to help others.

1. Adding extra fields to standard tables will render your installation  not upgradeable using normal means.
2. To achieve the same result, make yourself an extension with an additional table with a 1:1 relationship with the parent table (read the wiki and the forum on how to create one) and install it.
3. If the data is trivial, put it into a memo / text field that already exists (remarks, details, description, etc) and use the non field db data method illustrated in adding Bin Locations to Packing Lists.

Bumped the build and committed in my GitHub Repo.

@joe: Can take it from there and update repo.

In FA 2.3 some tables are MyISAM and others are InnoDB.
In FA 2.4 all tables are InnoDB.

Since you were using a debian server - which version od debian and which version of MySQL were you using?

I just created a FA db with utf8 and persian collation in XAMPP v1.7.3 and then turned off the MySQL server.

I then replaced all files in the MySQL data folder's FA db folder with the ones extracted from your zip file and then start the MySQL server.

You can then use phpMyAdmin to do some diagnostic checks and repair if needed and identify the corrupt tables and replace them with ones from the standard sql/en_US-new.sql file after altering the collations.

All InnoDB table data files have only the .frm extension and none other. In some instances there will be some .ibd files as well.

Here are some references:

Ref 1 : http://www.fromdual.com/recover-lost-frm-files-for-innodb-tables

Ref 2:http://dba.stackexchange.com/questions/16875/mysql-how-to-restore-table-stored-in-a-frm-and-a-ibd-file

Ref 3: http://www.hexblot.com/blog/recovering-innodb-tables-ibd-and-frm-files

Ref 4: http://www.thegeekstuff.com/2014/04/recover-innodb-mysql/

Ref 5: http://egil.biz/how-to-recover-mysql-data-from-innodb/

Ref 6: http://www.bluegecko.net/mysql/recovering-a-schema-from-innodb-frm-files/

Do you still have the filesystem of the Debian server?

Tell us the menu items you clicked in order to get the "sales invoice register" so that we can let you know how to get "purchase invoice register" done in FA.

Does this satisfy your needs?

@asgare: Attached is your full sql set that you can populate into your database. All missing tables have been populated with just the schema.

Lessons learned: To recover InnoDB tables, you will need the InnoDB cache(ibdata1, ib_logfile0, ib_logfile1) by taking the zip of the entire MySQL data folder after stopping the MySQL server.

As a trusted ERP that FA is, the sales register is designed to be not easily editable. Just void the invoice and create a new one.

For Purchase Invoices refer this post.

Purchases => Supplier and Purchasing Reports => Supplier balances => Filter Supplier.