It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by apmuthu
Have a look at the templates folder in the said module. There are 9,10,11 or 24 commas in each field in the CSV files there.
Your data set seems to be following the templates/bank_en_GB.csv file.
Which CoA are you using? The UK CoA has some errors in field order.
Check out the corrected extensions and CoAs in my unofficial GitHub Repo.
Replace the users.password field value with a known one like "5f4dcc3b5aa765d61d8327deb882cf99" and use the string "password" to login.
The users.user_id field has the username.
Use appropriate table prefix as needed.
Wiki-ed it under Workarounds in the Quick Entries page.
Such information in FA 2.3.x can be stored as part of the stock_master.long_description field and used as in the Wiki Article on Bin Locations.
In FA 2.4, a separate field in the stock_master table to provide for BinLocation would be useful.
Need to provide link to your codebase for possible assistance.
"JavaScript Intention Power Pack" is not part of standard FrontAccounting. Unless proper context is provided, assistance would be impossible.
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?
Try to use the latest snapshot in the FA 2.3 series.
The extensions are in my unofficial github repo.
The company folder will have to be writeable anyway.
You can run a mail server on a dummy local domain (windows fake sendmail, etc) and then you can forward it with any addendum to those within your organisation.
Please post each issue in separate posts.
Study the existing reporting/repXXX.php file to make your own alignments - see attachment for example.
If ($brain_smashed)
echo "Seek professional assistance.";http://www.w3schools.com/tags/att_meta_http_equiv.asp
http://www.metatags.info/meta_http_equiv_refresh
When a new GL Account is added, it shows the value of the Account Code as not editable and hence the form is not suitable for entering a new record and to do that the ajax in the top dropdown box achieves it.
Alternatively, a link to the new account page can be formed as a button as shown in the attachment.
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.
By inserting a field in your db table how do you expect it to get populated with any value without providing it in a form to acquire it - the form needs to be displayed anyway along the the label and form field for the newly added field in the FA table.
Please post your exact requirements and offer for customization in the Jobs wanted/offered, non-free offers topic.
@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.
Attached is an InnoDB recovery manual PDFed and attached here.
Bumped the build and committed in my GitHub Repo.
@joe: Can take it from there and update repo.
Please use the latest snapshot instead of the release version.
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
InnoDB tables cannot be copied the same way that MyISAM tables can.
Just copying the .frm and .ibd files from one location to another is asking for trouble. Copying the .frm and .ibd file of an InnoDB table is only good if and only if you can guarantee that the tablespace id of the .ibd file matches exactly with the tablespace id entry in the metdata of the ibdata1 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?
Post your custom report requirements in the Jobs wanted/offered, non-free offers board.
Check out all the reports available in FA in the Wiki.
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?
Purchases => Supplier and Purchasing Reports => Supplier balances => Filter Supplier.
The FA 2.3 InnoDB lost tables schema is attached for utf8_unicode_ci collation.
@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.
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.