Many of ApniTally readers have posted me queries related to proble
Here is my answer to these queries.
Going by the experience which i have got from Tally I would like to say that if you are using a version and it is running smoothly then you should never think to upgrade directly on your live or current data unless and until some new feature is there and you are in dire need of that feature. Data conversion from lower release to higher release is very easy but from higher release to lower release it is not that much easy.
Reader may think if Tally is not to be upgraded then why Tally people are upgrading every 15 days? Here i would like to say that new release normally have some modifications etc which some times may not be needed to some people. Where as some users of some states may not need that upgrade. More over a stable release which is working and a condition where new feature is not needed up gradation is not advisable. There are chances that newer release may bring problems with it.
Here are few solutions to overcome possible upgradation problem
1. When ever you change the release then first thing you should keep in mind is always take a backup of data before converting.
2. Try new upgradation on separate location and separate data so that original data can be protected.
3. Give some days of try to new upgrade so that possible errors if come can be seen on demo data. Only after satisfaction of problem free functioning new upgradation should be put into full practice.
Going by the experience which i have got from Tally I would like to say that if you are using a version and it is running smoothly then you should never think to upgrade directly on your live or current data unless and until some new feature is there and you are in dire need of that feature. Data conversion from lower release to higher release is very easy but from higher release to lower release it is not that much easy.
Reader may think if Tally is not to be upgraded then why Tally people are upgrading every 15 days? Here i would like to say that new release normally have some modifications etc which some times may not be needed to some people. Where as some users of some states may not need that upgrade. More over a stable release which is working and a condition where new feature is not needed up gradation is not advisable. There are chances that newer release may bring problems with it.
Here are few solutions to overcome possible upgradation problem
1. When ever you change the release then first thing you should keep in mind is always take a backup of data before converting.
2. Try new upgradation on separate location and separate data so that original data can be protected.
3. Give some days of try to new upgrade so that possible errors if come can be seen on demo data. Only after satisfaction of problem free functioning new upgradation should be put into full practice.
So coming to basic question of upgrading to release 3 beta i would like to share that beta is for testers only. It is having many problems and users should avoid the release to their live data. Although keeping in mind above steps it can be done or be wise and wait for final release 3.