prashants / webzash

Easy to use web based double entry accounting software in PHP - MySQL under MIT License
http://webzash.org
Other
211 stars 108 forks source link

Recommendation for retroactive accounting #153

Closed jessicana closed 3 years ago

jessicana commented 3 years ago

Hello Sir! I want to enter the accounting transactions for company ABC LLC since its inception in 2014 up to the current year, 2021. This will require eight years of accounting that I will keep open in the system until the IRS audits the records and I get the tax returns certified. I will keep recording transactions for all years without closing any of them (i.e., I will keep them unlocked). What is the best practice I can follow to do that in Webzash?

What I tried to do but it did not work is going to Administrator Dashboard > Create Account > and I used the same database details, but it showed errors (I left some examples below). Do you think I have to create eight databases, one for each year? Can't I maintain all of the accounting years on one database?

Table with the same name as "entries" already existsin the "databasename" database. Please, use another database or use a different prefix.

Table with the same name as "entryitems" already existsin the "databasename" database. Please, use another database or use a different prefix.

Table with the same name as "entrytypes" already existsin the "databasename" database. Please, use another database or use a different prefix.

Table with the same name as "groups" already existsin the "databasename" database. Please, use another database or use a different prefix.

Table with the same name as "ledgers" already existsin the "databasename" database. Please, use another database or use a different prefix.

Table with the same name as "logs" already existsin the "databasename" database. Please, use another database or use a different prefix.

etc... 
prashants commented 3 years ago

Yes you need to create 8 database. I dont support multiple years accounts like the one you are trying to setup. If you have some restriction on database creation then you can try using database table prefix which will give different table prefix for each year within same database.

You already have account and you are creating another one over it hence the error.

jessicana commented 3 years ago

Thank you very much! The table prefix worked like a charm. For example, for 2014, I used _14, and the accounts were created promptly on my testing stack. Do you recommend multiple databases, or am I safe using database table prefixes in my case? I have no restrictions on creating databases, and I will go for your recommendation on best practices for webzash. If multiple, I will make them.

prashants commented 3 years ago

It's table prefix not suffix :) You should use 2014_ and not _14.

I recommend separate databases. Easier to backup and restore. Once accounts for a particular year are completed, you can take backup of the database once and forget about it.

On Wed, Sep 22, 2021 at 11:54 PM jessicana @.***> wrote:

Thank you very much! The table prefix worked like a charm. For example, for 2014, I used _14, and the accounts were created promptly on my testing stack. Do you recommend multiple databases, or am I safe using database table prefixes in my case? I have no restrictions on creating databases, and I will go for your recommendation on best practices for webzash. If multiple, I will make them.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/prashants/webzash/issues/153#issuecomment-925177097, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQULHVGNIHES5UPWIFTLDUDINNRANCNFSM5EQG6BOA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.